Hydra | 397 Members | |
| 113 Servers |
| Sender | Message | Time |
|---|---|---|
| 11 May 2026 | ||
| that also cuts down on traffic between the queue ruunner and the builder | 20:03:54 | |
| the current thing is how really old remote building worked | 20:04:09 | |
| the thing I am going to is how hydra workedf or the last decade or so | 20:05:28 | |
I was not sure which setting is actually required because it didnt work after just enabling services.hydra-queue-builder-dev.useSubstitutes = true; (on the builder) so I also set nix.settings.builders-use-substitutes = true (I am not sure where i found that) and this is of course also set nix.settings.substituters = ["https://cache.nixos.org" "https://cache.MY CACHE"] | 20:07:01 | |
| yeah taht sounds like it should work | 20:08:56 | |
| it is just hard to debug right now I am afraid with the dependency drvs being disclosed to the builder | 20:09:15 | |
| you could try to check nix logs and figure out what it is doing what it is doing | 20:09:28 | |
| but that is hard | 20:09:31 | |
| (the decision to build the stuff is nix's) | 20:10:28 | |
| This is the process running right now
So it picked the first drv that is not in the cache and tries to build it but | 20:15:15 | |
| Thats whats confusing me, how is it supposed to work? When the builder is missing dependencies, should nix get them because substitutions should be on, should the queue-builder get them from the cache or should the queue-runner send them to the builder? | 20:21:45 | |
| interesting, I am not sure where that is coming from | 20:34:42 | |
| oh nevermind I do see it | 20:35:24 | |
that is in subprojects/crates/nix-utils/src/realise.rs | 20:37:02 | |
git log missed it becasue it was there since the initial commit (?) | 20:37:17 | |
| oh because I was git loging the specific file | 20:39:10 | |
| Frooastside: the instent is that the new builder and new queue runner will cooporate to get the inputs in place separately | 20:40:09 | |
| so nix shouldn't need to download anything | 20:40:16 | |
| but clearly that is not working right yet | 20:40:20 | |
| Ok, thank you | 20:41:05 | |
| 12 May 2026 | ||
| FYI https://nixos.org/hydra/manual/ seems broken due to CORS rules | 03:51:51 | |
| Any sense where they're coming from? Took a quick look in https://github.com/NixOS/infra/blob/main/build/hydra-proxy.nix to fix it but didn't see anything | 03:53:31 | |
| I tried getting the old queue-runner working but i face a weird issue where it just gets stuck on "sending inputs..." it tries to copy things from the s3 store but never finishes im not even sure whats the problem there. the only option is to manually kill the nix-daemon processes, systemctl restart nix-daemon doesnt touch the stuck processes. after doing that i can manually copy the nix store paths though im not sure if it works manually because its only one at a time or something else | 09:10:28 | |
| 18:14:22 | ||
| Can the new queue-runner serve as only a coordinator/scheduler, but not perform any build/signing actions on it's own (eg: without even having a functioning Nix store locally?). Use-case: CI with ephemeral builders needing a centralized coordinator. | 20:49:03 | |
| yes, it can | 20:49:24 | |
| using pki for onboarding new nodes and the presigned urls feature to decentralize uploading | 20:49:59 | |
I think the problem might have been nix.settings.auto-optimise-store = true it seems to work now (for at least 2 minutes and it stopped every 10 seconds or so) | 22:31:22 | |
| 15 May 2026 | ||
| Took me some time. I will only respond in one message to all of your messages so I don't have to use the shitty matrix quote feature too much. I usually read my Matrix many times a day, the reason I seem so unresponsive is the dreadful feeling of opening this group or interacting with the repo in general that has taken over. Thank you for all the responses, but it still didn't address stuff like the short-time self-merges (~1h for the most recent one) and the overall overly high velocity on refactorings that don't seem to be really critical at all to take the new runner into production. About both the LLM thing and the toml-formatter thing: These are technical issues and that's not what is draining all motivation and energy to do any Hydra work. It's only a human issue (to me, at least). I have gotten to the point where I just delete mails for the Hydra repo without even reading the title because it doesn't even feel like it still matters to take a look | 17:46:12 | |
| Janne: we can find a compromise, but I want to be clear that lots and lots of refactoring is something that brings me joy, and is also how I get to know the code that was written last year | 19:58:33 | |