| 27 Mar 2026 |
 John Ericson | sounds good! | 17:01:10 |
| John Ericson | https://github.com/NixOS/hydra/pull/1605/files btw if anyone wants to review that | 17:02:03 |
| John Ericson | it remoes the last C++ :) | 17:02:10 |
| John Ericson | BMG: Is there a valid reason that drvPath is nullable on BuildStep? | 20:51:11 |
| John Ericson | Also it seems like Build / BuildOutput is full of redundant stuff and we should instead track the root BuildStep? | 20:51:42 |
|  Artemis Tosini (NixOS) joined the room. | 20:53:57 |
| John Ericson | (when you see this BMG, please ping Artemis Tosini (NixOS) too) | 21:01:42 |
|  Sapii joined the room. | 22:49:00 |
 BMG | Not off the top of my head but I might have it documented somewhere. It was buildstepoutputs I was looking at | 23:11:43 |
| 28 Mar 2026 |
 Janne | Tbh, the crurent velocity is a bit extreme imo and the speed gives a lot of viebecoding vibes. We still have not deployed the new qr to staging (let alone production) and are adding more and more changes on top of master that will have to be deployed along all fixup commits for the new qr when something goes wrong in production. I am obviously very happy to see C++ removed but I also fear a very high chance breakages - see the Nix/S3 debacle that was Claude-powered | 11:37:51 |
| Janne | We actually have a custom plugin for that that was never as generic as what the PR does … I wonder if we should allow for multiple providers while we're at it. Might be able to remove the Google tracking (or google altogether) from Hydra which has been annoying me for a long time now with h.n.o | 11:38:41 |
| Janne | 
Download image.png | 11:39:36 |
| Janne | These requests in particular | 11:39:39 |
 tomberek | I was looking at doing some Hydra hacking, but not sure what is currently expected to pass tests and what would be new breakages. My guess is that we're in a transition period? | 21:36:37 |
| tomberek | (was looking at: https://github.com/NixOS/hydra/pull/1518) | 21:36:41 |
| 29 Mar 2026 |
| John Ericson | To be clear, that PR should definitely go to staging first, and should not hold up the deployment to prod | 15:59:22 |
| John Ericson | the other changes I have read at code review time quite closely, and I would not be so concerned | 16:00:10 |
| John Ericson | I definitely agree we don't want a buch more dev to pile up and then we end up with something that cannot be deployed | 16:01:01 |
| 30 Mar 2026 |
| Janne | Only the AI overlords can tell by now | 13:25:05 |
| 6 Apr 2026 |
|  whispers [& it/fae] joined the room. | 05:55:06 |
|  Hythera joined the room. | 21:49:44 |
| 7 Apr 2026 |
|  Proesmans Bert joined the room. | 18:48:23 |
| 8 Apr 2026 |
 Mic92 | Hands up who is using Hydra with non-git / non-flake inputs especially VCS like mercurial/darcs/svn. | 09:21:53 |
| Mic92 | I am thinking that we might want to reduce the feature scope of hydra a bit. | 09:22:10 |
| Mic92 | * Hands up who is using Hydra with non-git / non-flake inputs especially version control systems like mercurial/darcs/svn. | 09:22:24 |
| Janne | Throw out the channels as well while you're at it | 14:21:42 |
 Sandro | I have overwritten them them with null since forever 😂 | 14:25:18 |
 hacker1024 | We're using text, Nix expression, Boolean inputs etc. to configure certain jobsets | 14:26:50 |
| John Ericson | Simon Hauser: does long term more harmonia for local store and/or hydra database for derivations sound acceptible for you in place of more ffi for now? | 15:08:46 |
| John Ericson | Simon Hauser: I am redoing it with aterm and the physical path | 15:53:44 |
