Open Source Maintenance, 2024-07-14

No video

Open Source Maintenance, 2024-07-14

Рет қаралды 19,600

Jon Gjengset

Күн бұрын

Пікірлер: 26

@smallclover Ай бұрын

I love these Open Source Maintenance VODs since it's so cool to see behind the scenes of a repository/package maintainer like this and how much work goes into it.

@ProjectFinalAudio Ай бұрын

Really inspiring! Thanks for maintaining all the open-source projects.

@brandonkauffman7256 Ай бұрын

Thanks for the day in the life show. I work as devops/sre and I enjoy using Rust and watching your stream 1. to learn about awesome rust things and 2. to feel like I'm working in the office again.

@cocacodes Ай бұрын

This whole VOD felt so frustrating to watch, 10/10

@rodelias9378 21 күн бұрын

I watched this from start to finish.. and man.. this open source stuff requires a lot of time and work! Great stream Jon and thanks for everything you do!

@waynelau3256 22 күн бұрын

I really wish my ADHD doesn't restrict me from watching this for 6hours, thank you for the quality content even though i struggle to watch 😂

@FerPerez-mc3wr 28 күн бұрын

The content is a cut above the rest. Keep setting the bar high!

@polares8187 Ай бұрын

Please do more crust of rust. They are incredibly informative

@kunal..... 23 күн бұрын

Don't you get burned out??

@kunal..... 23 күн бұрын

Really fucking inspiring

@uncleyour3994 Ай бұрын

6 hours, wow

@dzuchun Ай бұрын

git bisect around 5h40m really felt more like git blame 😅

@ferdynandkiepski5026 Ай бұрын

I don't think you actually needed to install nasm. After setting that environment variable it would build without it. Would it be slower? Yes, probably by a lot as well. Does it matter for CI? I don't think so. Would also require an unoptimized build of it.

@jonnyso1 24 күн бұрын

Funny, I failed an test on a job interview a year ago and I've been all this time wondering how I could actually do what they asked the way they asked, I had no idea something like Fantoccini was a thing.

@YuruCampSupermacy Ай бұрын

Wait 6hrs of coding non stop? Really? Is that even humanely possible?

@nosh3019 Ай бұрын

I think we’re not talking about human here

@kunal..... 23 күн бұрын

I don't know how

@danielegger6460 Ай бұрын

I'd always do a cargo publish before pushing to git. Otherwise, if cargo publish fails in one of it's misterious ways, you'd have to change the history of the repo to if a change is required to make publish work.

@jonhoo Ай бұрын

Then you'd lose the commit hash in the vcs file that Cargo sticks in the crate file though?

@danielegger6460 Ай бұрын

@@jonhoo Not sure which vcs file you mean, I haven't seen `cargo publish` modify any files in the repo.

@jonhoo Ай бұрын

doc.rust-lang.org/cargo/commands/cargo-package.html#cargo_vcs_infojson-format

@danielegger6460 Ай бұрын

@@jonhoo Why wouldn't that be accurate? Cargo publish requires you to commit all relevant files before allowing you to publish. So the changes to Cargo.toml etc. would all be part of the branch that would be pushed if and once the publishing succeeds. If cargo aborts the process you get to do over, if you pushed the branch and tag before the publishing, if it aborts, then you either have to rewrite the git history or do another version bump (and so on until it succeeds).

@jonhoo 29 күн бұрын

Oh, I see what you mean. I thought you also wouldn't commit. Even if you do though, I'd be slightly worried that you then push and end up with failing CI or some such. Or alternatively if you have a branch with succeeding CI that something then lands on main in the meantime. But then again, I suspect every ordering here has some possibility of a race.

@dzuchun Ай бұрын

it's ALWAYS windows 😢

@dzuchun Ай бұрын

"This job failed. Ok, great."