| 6 Mar 2025 |
 ghpzin | * I assumed it would use json api endpoints for that, if you still crawl every build by id after pulling list from eval.
https://github.com/NixOS/hydra/blob/master/doc/manual/src/api.md | 20:04:40 |
 polygon_ | I already got all of that from the HTML list, but for the log I'd need the drv-path with the store hash: 3ipspns3k0gk8v9yp775w0blg8l6mm5w-clasp-2.6.0.drv | 20:05:26 |
| polygon_ | I probably go with evaluating locally, it's just a subset of 400 packages | 20:06:17 |
| 7 Mar 2025 |
| polygon_ | Thanks for the help yesterday, list with still failing builds after gcc-14 update is complete: https://polygon.github.io/fix-nixpkgs-gcc14/ | 15:43:18 |
| 10 Mar 2025 |
|  @aftix:matrix.org joined the room. | 05:18:27 |
| @aftix:matrix.org | what's the magic to get LDAP auth to work on hydra? looking at the debug logs, my hydra can bind, correctly find the LDAP user, correctly find the LDAP groups, and then send the correct password to re-bind as the LDAP user (which works with ldapwhoami), but logging into my admin account gives "bad username or password" and my user account gives "no attribute cn for User" (there is a CN attribute according to ldapsearch and my hydra configuration doesn't mention CN anyway, just name) | 14:24:37 |
| 17 Mar 2025 |
|  jappie joined the room. | 08:08:47 |
|  griff changed their display name from griff79 to griff. | 17:24:15 |
