| 15 May 2026 |
 Janne | 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 |
 John Ericson | 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 |
| John Ericson | there is a a bit of an inherient trade-off in here in that if I do less, you might feel better, and might help me figure out what is going wrong with prod, but I will be doing less (quite literally) and I will be learning the code less | 19:59:21 |
| John Ericson | IMO the state of this repo being unable to be deployed is not good a high risk state, but consider also I can stop refeactoring --- my prefered way of finding the problem --- and then I hope you are less burnt out? but we're gambling on psycology here. Say you still feel burnt out, and meanwhile the clock is ticking for me to get this stuff done | 20:00:45 |
| John Ericson | your welcome to look at any older commit and try to debug that, and if you get it working, I will have no problem deploying that older commit | 20:01:19 |
| John Ericson | and we can re-review what is on master since then | 20:01:25 |
| John Ericson | Janne: if roadmap would make this all more scrutable, the refactors I've done the last few days are all in prep for trying to only send resolved derivations to the builder in order to make the building dependnecies by mistake isssue impossible | 20:12:46 |
| John Ericson | well I should say almost all. In conjunction with that I am looking to replace the FFI with the daemon protocol because of the SQLIte errors we saw, and trying to be less tied to an exact nix version (since itis C++ FFI ATM) | 20:14:05 |
| John Ericson | The FFI was my idea I requested of Simon Hauser but I regret doing so because I didn't realize on macOS especially the daemon would be used anyways, so it would be FFI just to do the daemon protocol anyways | 20:15:38 |
| John Ericson | that reminds me we should actually test no local nix store in the presigning case | 20:16:39 |
| John Ericson | ideally we can do some/all of the tests both ways | 20:16:55 |
| John Ericson | rather than write new tests from scratch | 20:17:00 |
| John Ericson | I do have a NixOS test for presigning and it would be fun to disable the host nix store on that | 20:17:18 |
| John Ericson | I suppose it might be a problem for evaluations though | 20:17:34 |
| John Ericson | maybe after those are distributed | 20:17:37 |
| Janne | Why is the clock ticking? I am not aware of a release cycle to catch in hydra? | 21:04:53 |
 hexa | The primary work should be enabling whomever can fix the scheduling in the queue-runner, because all other work is basically pointless if nobody wants to deploy the queue-runner in the state it is right now. | 21:05:42 |
| hexa | nixos/infra is pinned and so is my private hydra | 21:06:05 |
| Janne | * Why is the clock ticking? I am not aware of a release cycle to catch in hydra? The answer to that would probably also explain the insane velocity the repo currently has (for no apparent reason from my perspective) | 21:06:13 |
| Janne | Which may give me additional headache (not sure if there will be conflicts) to have to rebase the upcoming security patches for h.n.o | 21:06:53 |
| John Ericson | the click is ticking is my own client work that allows me to work 100% of the time on hydra | 21:07:04 |
| John Ericson | the actual feature work is all basically all done hydra side | 21:07:29 |
| John Ericson | but that is equally pointless if the thing is broken and cannot be deployed | 21:07:41 |
| Janne | I'm a bit too tired to come up with the proper words for what I think so I think I will have to postpone that to tomorrow (from my perspective) | 21:10:12 |
| John Ericson | ideally, the new queue runner was going to be finsished and deployed jan/feb, before I even started | 21:10:16 |
| John Ericson | sure, have a good friday evening | 21:10:45 |
| John Ericson | OK yay the daemon protocol refactor is now passing the test suite locally | 22:31:08 |
| John Ericson | that's net -2000 lines of code :) | 22:31:20 |
| 19 May 2021 |
|  Eelco 😴 changed the history visibility to "world_readable" from "shared". | 15:39:32 |
|  Rev. CornWallace III (novus ordo seclorum) joined the room. | 15:40:25 |
