| 16 Jun 2021 |
 @grahamc:nixos.org | I was thinking in my head I guess it is a bit secret, but it isn't so hard to search the server / space for "hydra" :) | 20:32:23 |
| 17 Jun 2021 |
|  artturin set a profile picture. | 00:11:32 |
 Amanda (she/her) | Threw https://github.com/NixOS/hydra/pull/974 together when I was waiting for my weekly updates to build, at the very least it's making my homelab able to evaluate in hydra again. (stdenv.lib was removed in unstable recently) | 21:03:39 |
| Amanda (she/her) | will report back on if it can actually build | 21:04:03 |
| Amanda (she/her) | though I'm not sure why it wouldn't | 21:04:12 |
| @grahamc:nixos.org | thanks Amanda (she/her) :) | 21:18:50 |
| 19 Jun 2021 |
|  nf joined the room. | 06:48:05 |
| 21 Jun 2021 |
|  Taneb joined the room. | 13:57:24 |
| Taneb | It looks like Hydra is failing to build itself on unstable | 14:03:42 |
| @grahamc:nixos.org | the nixpkgs packaged version? | 15:01:47 |
| Taneb | Yeah | 15:03:25 |
| Taneb | e.g. https://hydra.nixos.org/build/145838218 | 15:04:24 |
| Taneb | Looks like it's because libpqxx was updated in nixpkgs | 15:04:52 |
 ma27 | The easiest option would be either a revert or a reintroduction as libpqxx_6. Otherwise I can try to fix the upstream issue at the end of the week (well, unless Graham is faster, of course :)) | 15:25:30 |
| @grahamc:nixos.org | from a 30s look it isn't clear to me what actually is broken :grim | 15:53:25 |
 cransom | it feels like running an up to date hydra without the flake is a losing battle now. there are depends that slip in that don't make it to the nixos release or unstable package. | 16:31:09 |
 das_j | Yeah, always great to depend on a thing that's not even relesed let alone stable | 18:29:36 |
| Taneb set their display name to Taneb. | 18:42:44 |
| 22 Jun 2021 |
| Taneb | Has there been any thought about making systemd-analyze security less upset by the Hydra units NixOS generates? | 08:38:09 |
| das_j | In reply to @taneb:hacksrus.uk
Has there been any thought about making systemd-analyze security less upset by the Hydra units NixOS generates? I can provide you with the units we use | 08:51:24 |
| das_j | well it's worse than I remembered:
hydra-check-space.service 9.6 UNSAFE 😨
hydra-compress-logs.service 9.6 UNSAFE 😨
hydra-evaluator.service 3.7 OK 🙂
hydra-notify.service 5.0 MEDIUM 😐
hydra-queue-runner.service 3.7 OK 🙂
hydra-server.service 3.7 OK 🙂
hydra-update-gc-roots.service 3.2 OK 🙂
prometheus-hydra-exporter.service 5.0 MEDIUM 😐
| 09:25:05 |
 Sandro | At least the emoji is not crying | 09:25:56 |
| Taneb | By default they're all 9.6 or 9.2 and... I really don't think they need to be | 10:01:04 |
| das_j | my units would probably be a lot better if I used CapabilityBoundingSet but I'm doing that with AppArmor because it's a lot less annoying. systemd doesn't detect that and therefore scores my units worse than they really are | 10:02:01 |
| @grahamc:nixos.org | it'd be great to improve them | 13:57:09 |
| @grahamc:nixos.org | anyone want to open a bug? | 13:57:35 |
| Taneb | https://github.com/NixOS/hydra/issues/977 | 14:49:20 |
 David Arnold (blaggacao) | https://demo.hedgedoc.org/s/RO9YawHcY# | 20:03:32 |
| David Arnold (blaggacao) | (ideas worth spreading?) | 20:03:51 |
 tomberek | In reply to @blaggacao:matrix.org
https://demo.hedgedoc.org/s/RO9YawHcY# I enjoyed this article. https://gregoryszorc.com/blog/2021/04/07/modern-ci-is-too-complex-and-misdirected/ I prefer to take it farther and even consider some batch data flows to be “indistinguishable from a build/CI system”. And it just so happens we have a powerful+flexible build system to utilize. | 20:13:50 |
