| 27 Aug 2024 |
 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 |
 Mindavi | That's the only attribute available anyway, but yeah | 12:01:38 |
| 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 |
| 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 |
| hacker1024 | And I'm not sure what are keywords or placeholders in the given command | 11:51:53 |
| hacker1024 | Or if Hydra needs to be stopped during this process | 11:52:21 |
| Mindavi | Hmm, maybe PostgreSQL updated? Normally this shouldn't happen, and nothing in the hydra schema changed | 13:50:17 |
| 2 Sep 2024 |
| das_j | It happens when the glibc version of postgres changes | 06:48:10 |
|  stigo joined the room. | 10:43:54 |
| 3 Sep 2024 |
| Sandro 🐧 | sudo -u postgres psql and run the command | 12:14:17 |
| Mindavi | Maybe something for the wiki | 17:48:25 |
|  noisersup joined the room. | 17:58:00 |
| Sandro 🐧 | that's pretty much standard postgres knowledge | 18:25:42 |
 Alyssa Ross | not necessarily standard Hydra knowledge though | 18:26:29 |
| Mindavi | I don't really feel qualified as a database admin but generally it goes fine for me, until I need to update major PostgreSQL databases | 19:41:54 |
| Mindavi | * I don't really feel qualified as a database admin but generally it goes fine for me, until I need to update major PostgreSQL versions | 19:42:12 |
| 5 Sep 2024 |
| dramforever | til to even use the postgres user, i've been using hydra | 02:06:43 |
| dramforever | unrelatedly | 02:24:20 |
| dramforever | how do the hydra people, so to speak, feel about adding additional meta attributes to the db into the builds table? | 02:24:44 |
| dramforever | basically i'm trying to see if i can (we can?) work around this https://github.com/NixOS/nix/issues/2742 in hydra by adding like meta attributes | 02:27:33 |
