Hydra | 392 Members | |
| 111 Servers |
| Sender | Message | Time |
|---|---|---|
| 14 Jan 2022 | ||
| hydra master of improv. | 17:43:56 | |
| I deleted a full nixpkgs eval jobset from my hydra yesterday and the query took >1h. Maybe my postgres isn't configured properly 🤷 | 17:44:22 | |
| hydra.nixos.org disabled deleting jobsets because of that | 17:45:28 | |
| I think cleaning up some FK's and indexes will make that much faster | 17:45:39 | |
| on that note, https://github.com/NixOS/hydra/pull/1109 brings us closer to doing that | 17:56:11 | |
| TIL you can have github trigger evaluations on push | 19:45:25 | |
| and it works on flakes: https://github.com/NixOS/hydra/pull/1110/commits/ee529c6c33b37ef76e33db685fe7fcc32312c187 | 19:46:40 | |
| 15 Jan 2022 | ||
In reply to @andreas.schraegle:helsinki-systems.dehttps://github.com/NixOS/hydra/pull/1114 | 01:39:21 | |
| and this PR is getting smaller: https://github.com/NixOS/hydra/pull/1093 | 01:49:00 | |
| chipping away at it, making PRs for each little bit | 01:49:07 | |
| 17 Jan 2022 | ||
| merged & deployed and it seems to be going fine :) whose next? 😉 | 16:00:20 | |
| 18 Jan 2022 | ||
| anyone seen errors like this one before?
| 20:21:19 | |
| * anyone seen errors like this one before?
| 20:21:39 | |
| shouldn't hydra 's queue runner be responsible for sending all the inputs? | 20:22:29 | |
| oh no this is when I go ham on the queue runner isn't it | 20:33:45 | |
| I hate this | 21:04:43 | |
| 19 Jan 2022 | ||
| this is interesting, the queue runner when creating the build step considers the derivation for the missing output but then doesn't do anything with it | 16:18:26 | |
| what I've found is it is checking to see if the destStore (an S3BinaryCacheStoreImpl) has it as a valid path:
it doesn't know (oUnknown) and falls through to:
and it does exist which ends up returning from there we're back in the queue monitor:
except the path is valid on the remote end despite not being on the local machine, so it never gets put in to "missing", so it never enters this:
at which point Hydra thinks it is ready to build a derivation where a dependent derivation's outputs are not available | 21:15:42 | |
| but I don't understand why it does work, substituting from the cache, in many ways. | 21:19:59 | |
| * but I don't understand why it does work, substituting from the cache, in many cases. | 21:20:01 | |
| if this rings any bells at all I'd be indebted | 21:26:50 | |
| 20 Jan 2022 | ||
| 00:14:01 | ||
| 18:54:02 | ||
| This is fishy. Hundreds of "queued jobs" but all have finished hours ago: https://hydra.nixos.org/eval/1739175#tabs-unfinished Fortunately, it didn't prevent the channel from advancing 😅 | 19:00:54 | |
| 21 Jan 2022 | ||
| https://github.com/NixOS/hydra/pull/1126 | 00:53:14 | |
| 05:15:02 | ||
I'm trying to set up a Hydra, following https://nixos.wiki/wiki/Hydra. I could successfully create an admin user for myself with a plain text password, but whenever I try doing it via hash (following the instructions in hydra-create-user --help) it tells me that the user was updated, but I always get "bad username or password". Any idea what I can do to debug this? | 05:18:33 | |
That is, I create the hash by entering a nix-shell -p libargon2, doing argon2 "$(LC_ALL=C tr -dc '[:alnum:]' < /dev/urandom | head -c16)" -id -t 3 -k 262144 -p 1 -l 16 -e, entering blub, pressing Enter (is that wrong?), then ^D, and specify the resulting hash as hydra-create-user myuser --full-name 'foo bar' --email-address 'foo@bar.com' --role admin --password-hash '$argon2id$v=19$m=262144,t=3,p=1$U3I1UGt6ekV4c09oeGZxTA$oQRySAPG6a6Wpao7wSQQ6w' | 05:23:53 | |
I just tried using the exact example line from hydra-create-user --help, user alice with password foobar, and it doesn't work either, so I guess something else is not working as expected here. Or maybe I misconfigured something, but so far everything should be copied from the article. Guess I'll stick with the plain text password for now. | 05:27:14 | |
* I just tried using the exact example line from hydra-create-user --help, user alice with password foobar, and it doesn't work either, so I guess something else is not working as expected here. Or maybe I misconfigured something, but so far everything should be copied from the article. Guess I'll stick with the plain text password for now and change it via the web interface. | 06:22:41 | |