| 28 Oct 2025 |
 Vladimír Čunát | We're spending a surprising amount of Hydra's "real time" on the added tests. | 17:07:04 |
| Vladimír Čunát | Hydra's eval itself tends not to be a real bottleneck. (though in CI it would be bad) | 17:08:03 |
| Vladimír Čunát | * Hydra's eval itself tends not to be a real bottleneck. (though in CI it would be very bad) | 17:08:14 |
 dish [Fox/It/She] | is there no way to parallelize the transaction by splitting it? | 17:35:27 |
| Vladimír Čunát | It would certainly help with the deadlocks and blocking other updates to the DB. | 17:36:33 |
| Vladimír Čunát | It often happens that Hydra stalls for several minutes because of such huge write transaction just happening. | 17:37:14 |
 K900 | There definitely is | 17:39:53 |
| K900 | Hydra is just an ancient Perl monstrosity | 17:40:00 |
 hexa | lol, I remember getting yelled at for nuking old aliases a while ago | 17:40:36 |
| hexa | the tl;dr is … just do it quietly? | 17:40:56 |
| hexa | or wait until we have a nixpkgs core team that can make that call? | 17:41:25 |
| Vladimír Čunát | runCommandNoCC will surely have some usage outside nixpkgs, too. | 17:41:50 |
| hexa | it was about e.g. pkgconfig = pkg-config back then | 17:42:07 |
 emily | it wasn't very quiet IMO… it's only ones that were already in 25.05 | 17:45:19 |
| emily | there was discussion about whether to go through a warning cycle for the ones without them or throw immediately | 17:45:41 |
| emily | we could still backtrack and attach warnings to those ones | 17:45:56 |
 Wolfgang Walther | Yeah, I'd say we could do that on a case-by-case basis, if there is reason for a specific case. | 17:46:27 |
| Wolfgang Walther | Was the argument that this should actually persist forever? If so, we'll just need to mark the alias as such instead. | 17:46:53 |
| emily | in practice unstable changes in ways that produce throws all the time I think, in this case it's at least a way that you can handle downstream without breaking compat with any supported release | 17:46:55 |
| emily | which AIUI has been the sticking point historically | 17:47:01 |
| emily | (anyway, this is just trying to prep for structured aliases which will automatically do silent → warning → throw → removed without all the manual work and eval issues wrangling this stuff manually causes right now :/ ) | 17:47:30 |
| hexa | it's not even in 25.05, it was probably removed earlier than that. no everything should be subject to a deprecation cycle IMO. | 17:47:39 |
| emily | to be clear, no Nixpkgs core decision on this | 17:47:50 |
| emily | anyway, putting a warning on runCommandNoCC seems reasonable enough to me | 17:48:21 |
| hexa | oh, it was utillinux 😄 | 17:48:47 |
| hexa | https://github.com/NixOS/nixpkgs/pull/192870 | 17:48:59 |
| emily | oh, gah | 17:49:18 |
| hexa | due to the node2nix abandonware | 17:49:20 |
| emily | I specifically dropped that one because I saw that node2nix was "handling it" since 2020 | 17:49:29 |
| emily | and forgot this particular nuance of how it "handles it" | 17:49:34 |
