| 10 Oct 2023 |
 raitobezarius | If Horg had to exist, I would start moving the Perl web part into a Rust web framework first | 15:56:27 |
| raitobezarius | We can keep the rest of Hydra as-is and perform a slow replacement | 15:56:39 |
 K900 | We also have a good amount of Rust in ofborg already | 15:56:41 |
| 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 |
