| 21 Aug 2024 |
 hacker1024 | In reply to @rick:matrix.ciphernetics.nl
Not that I'm aware of, and how can hydra know out doesn't change? Not sure what you mean by that exactly? If out changes, the path will change too. If the path exists, then it does not need to be rebuilt. | 12:06:26 |
| 22 Aug 2024 |
 Rick (Mindavi) | If debug changes I'm pretty sure out will always change too, unless it's a ca derivation | 08:29:43 |
 vcunat | Unless it's a unreproducible change. | 10:07:38 |
| vcunat | (same derivation but results not bit-for-bit equal) | 10:08:09 |
| 25 Aug 2024 |
| hacker1024 | Looks like https://github.com/NixOS/hydra/pull/1359 broke Hydra's .narinfo server quite significantly. After fixing two errors with https://github.com/NixOS/hydra/pull/1405, I am now stuck on the following. Does anyone have any ideas?
Caught exception in Hydra::Controller::Root->nar "Undefined subroutine &Hydra::Controller::Root::isValidPath called at /nix/store/kmpplf0rgdh7djzwbb9gbc3mdcc8k6im-hydra-2024-07-09/libexec/hydra/lib/Hydra/Controller/Root.pm line 333."
| 08:12:25 |
| Rick (Mindavi) | Consider adding a test to prevent future regressions at least, but no idea, never used that functionality | 08:41:08 |
| 27 Aug 2024 |
| Rick (Mindavi) | https://mastodon.delroth.net/@delroth/113029832631860419
FYI: unauthenticated endpoint for triggering evals | 05:03:50 |
|  oliver.falvai joined the room. | 10:53:17 |
|  @aloisw:kde.org left the room. | 17:26:30 |
 das_j | Mic92 and other committers: please temporarily abstain from merging things or pushing to master. we are requesting a CVE ID (again) and it would be lovely if the hashes don't differ from the announcement when we pick to master | 17:51:27 |
 Mic92 | Alright | 18:34:12 |
| Mic92 | janne.hess: are you working on a fix? | 18:35:40 |
| das_j | In reply to @joerg:thalheim.io
janne.hess: are you working on a fix? the fact that you are in the infra-build group means you can already see the advisory :D | 18:36:19 |
| Rick (Mindavi) | Lix hydra also has a patch publicly available, I saw | 18:45:21 |
| Rick (Mindavi) | Not sure if it covers everything but at least that endpoint | 18:45:33 |
| das_j | CVE ID got assigned and we have published the advisory: https://github.com/NixOS/hydra/security/advisories/GHSA-xv29-v93r-2f5v | 18:57:51 |
| das_j | In reply to @rick:matrix.ciphernetics.nl
Lix hydra also has a patch publicly available, I saw We do things a bit differently though by adding another role so the decision whether someone can trigger evals is more granular | 18:58:45 |
| 28 Aug 2024 |
 dramforever | do i have to get hydra_unstable if i want to get the fix? | 11:53:57 |
| Rick (Mindavi) | That's the only attribute available anyway, but yeah | 12:01:38 |
| Rick (Mindavi) | There's a PR in flight to rename it because it is the only attribute name | 12:01:57 |
| dramforever | oh, well, lol | 12:16:21 |
| dramforever | should have checked | 12:16:24 |
 Sandro | In reply to @rick:matrix.ciphernetics.nl
That's the only attribute available anyway, but yeah why does it have _unstable suffix then? | 13:08:48 |
| Sandro | In reply to @rick:matrix.ciphernetics.nl
There's a PR in flight to rename it because it is the only attribute name from me 😅 I think 3rd try or so | 13:08:59 |
| Rick (Mindavi) | Yeah, I'd like to go for it this time 😁 | 13:10:00 |
| 31 Aug 2024 |
| hacker1024 | I am getting a lot of these messages from hydra-server and hydra-send-stats after upgrading nixos-unstable. Is there a manual step that needs to be done? I did not change my system stateVersion.
WARNING: database "hydra" has a collation version mismatch
DETAIL: The database was created using collation version 2.38, but the operating system provides version 2.39.
HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE hydra REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.
| 11:47:24 |
| hacker1024 | * I am getting a lot of these messages from hydra-server and hydra-send-stats after upgrading nixos-unstable. Is there a manual step that needs to be done? I did not change my system stateVersion.
WARNING: database "hydra" has a collation version mismatch
DETAIL: The database was created using collation version 2.38, but the operating system provides version 2.39.
HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE hydra REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.
| 11:47:36 |
| hacker1024 | * I am getting a lot of these messages from hydra-server and hydra-send-stats after upgrading nixos-unstable. Is there a manual step that needs to be done? I did not change my system stateVersion.
WARNING: database "hydra" has a collation version mismatch
DETAIL: The database was created using collation version 2.38, but the operating system provides version 2.39.
HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE hydra REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.
| 11:47:42 |
 K900 | It literally tells you what to do | 11:49:50 |
| hacker1024 | I am not familiar with SQL or SQL servers in general. Am I supposed to use some tool to open a PostgeSQL console? | 11:51:19 |
