| 10 Oct 2023 |
 raitobezarius | Yeah, let's not make this go to waste | 15:56:54 |
| raitobezarius | Also, Rust FFI bindings to Nix are closer than Haskell FFI bindings to Nix in the context of the C stable API PR | 15:57:16 |
| raitobezarius | Arguably, Go FFI bindings are even done by that logic | 15:57:25 |
| raitobezarius | I can put up a plan of what needs to be done to go for Horg | 15:57:48 |
 K900 | Are we all just calling it horg now | 15:58:05 |
| raitobezarius | But I cannot drive any implementation work before Feb 2024 | 15:58:05 |
| raitobezarius | Well you really wanted it to be called Horg, right? :D | 15:58:21 |
| raitobezarius | I think it's a good name given that I am really bad at naming | 15:58:44 |
| 11 Oct 2023 |
|  @nam3l33ss:matrix.org changed their profile picture. | 19:34:11 |
| 12 Oct 2023 |
|  @erremilia:matrix.org set a profile picture. | 00:13:15 |
| @erremilia:matrix.org removed their profile picture. | 00:14:45 |
| 13 Oct 2023 |
 Christian Theune | raitobezarius: replacing stuff part by part sounds reasonable to me, specifically starting with the UI and then have the flexibility there to revisit architectural choice in the underlay. | 05:08:41 |
| Christian Theune | In the meantime, at the Flying Circus we have some issues with Hydra that I wonder whether we could pay anyone to fix or mitigate them. | 05:09:05 |
| Christian Theune | For example, I keep running into issues with the Github PR builder (not sure whether that's relevant or would happen in other situations as well) where you can't - for the life of it - trigger a proper re-evaluation after a force push. | 05:09:42 |
| Christian Theune | Or the queue runner is apparently a bottleneck for s3 uploads and then doesn't run any other jobs in the meantime while consuming 300% CPU for packing stuff ... o_O | 05:10:06 |
| Christian Theune | From my perspective it could make sense to try and fix those in the current code base so they can be used as input for whatever comes next. | 05:10:48 |
| Christian Theune | I'm noticing that nobody here currently has the reflex to add those issues to the issue tracker as the situation is generally considered "nothing happens anyway". | 05:13:26 |
| Christian Theune | (here = at the FC) | 05:13:33 |
 vcunat | Yes, hydra.nixos.org often does seem limited primarily by "Copying Results" phase, presumably the compression step. | 08:35:55 |
| vcunat | (network links certainly aren't much utilized when it happens) | 08:36:11 |
 @lotte:chir.rs | yeah, ideally there would be a way to run the copy step in the background | 09:14:29 |
| @lotte:chir.rs | my current hydra instance adds it as a runcommand hook right now, but previously i have used nix post-build hooks | 09:15:48 |
| @lotte:chir.rs | my current hydra config adds it as a runcommand hook right now, but previously i have used nix post-build hooks | 09:16:26 |
| @lotte:chir.rs | my current hydra config adds build results to a queue as a runcommand hook right now, but previously i have used nix post-build hooks | 09:16:45 |
| 15 Oct 2023 |
|  meet changed their display name from meet to meetm. | 07:05:59 |
 woobilicious | In reply to @raitobezarius:matrix.org
Plus, as much I am a type theorist, Rust type system has IMHO the right level to focus on the matter at hand rather than building castles of abstraction (which would make sense for other stuff, but not things like Hydra IMHO) That's a surprising take since rust seems like it was designed to do more low level, manual management of memory safely. While we just want to interact with some high level stuff like S3 and github, website? you'd get a long way with Haskell web framework and a little abstraction, without having to think too much about it, especially since it' has a real runtime with garbage collection & green threads. I do agree however with the pragmatic stuff like C-FFI, code reuse and accessibility. | 09:24:06 |
| woobilicious | Rust's lack of uninitialised, heavy used of optional, careful type design, and borrow checker does solve like 99% of the issues I have with every other language. | 09:33:18 |
| vcunat | hydra-queue-runner is quite performance-critical and I don't think the task would be suitable for Haskell. | 11:51:20 |
| vcunat | (build-step graph with like a million nodes in memory, scheduling that, etc.) | 11:52:19 |
| K900 | Honestly | 11:52:24 |
