| 30 Mar 2022 |
 Amanda (she/her) | ... The stars must have re-aligned, now it's also rebuilding fine without --cores 1 | 16:19:12 |
| Amanda (she/her) | Going on the 5th rebuild now and it's been fine | 16:19:28 |
| Amanda (she/her) | Maybe it's just more reliable on my laptop? Going to scp the folder up to the NUC homelab and see how it fares there | 16:22:45 |
 ajs124 | Are the two machines running different kernels?
I've had some spooky issues with impurity caused by different kernels, before. | 16:24:35 |
| Amanda (she/her) | my laptop's a single patch release ahead | 16:26:42 |
| Amanda (she/her) | 5.15.29 vs 5.15.28 | 16:27:11 |
| Amanda (she/her) | Hrm. Load jumps to ~10 when building hydra locally on the NUC | 16:36:09 |
| 1 Apr 2022 |
 hexa | hydra updates are sadly blockedd by the zlib issue | 23:03:07 |
| hexa | e.g. https://hydra.nixos.org/eval/1752452?filter=compress&compare=1752422&full=#tabs-now-fail | 23:03:54 |
| 2 Apr 2022 |
| hexa | how do people garbage collect hydra gcroots in an automated fashion? | 19:53:30 |
 das_j | In reply to @hexa:lossy.network
how do people garbage collect hydra gcroots in an automated fashion? hydra-update-gcroots.service? | 19:54:20 |
| hexa | guess I have to configure my hydra better then | 19:55:37 |
| hexa | so if I understand this right hydra should delete gcroots that are older than a day automatically? | 20:06:03 |
| das_j | In reply to @hexa:lossy.network
so if I understand this right hydra should delete gcroots that are older than a day automatically? If I remember correctly | 20:21:47 |
 @grahamc:nixos.org | And keepnr | 20:28:09 |
| hexa | and keepnr=0 has no special meaning? 😛 | 20:29:11 |
| 3 Apr 2022 |
| @grahamc:nixos.org | No :) | 02:13:38 |
 sterni | Can someone please fix hydra-unstable in nixpkgs? | 13:04:59 |
| @grahamc:nixos.org | In reply to @hexa:lossy.network
hydra updates are sadly blockedd by the zlib issue not sure the status of this, maybe you can check it out? | 13:08:13 |
| sterni | it's already broken in master something in the C++ side of things | 13:21:36 |
| sterni | or rather in the current channels | 13:22:25 |
| @grahamc:nixos.org | not sure, might be worth filing a bug | 13:30:46 |
| @grahamc:nixos.org | probably in nixpkgs, hydra itself builds | 13:31:17 |
| 4 Apr 2022 |
 niksnut | Anybody know what can cause this (running foreman in a nix develop shell):
$ foreman start
Warning: the running version of Bundler (2.1.4) is older than the version that created the lockfile (2.2.20). We suggest you to upgrade to the version that created the lockfile by running `gem install bundler:2.2.20`.
Traceback (most recent call last):
2: from /nix/store/ycshcdssxcj9sjf6yzb1ydw4fcglf66y-foreman-0.87.2/bin/foreman:20:in `<main>'
1: from /nix/store/ggqacj06n6qfm1iww0bih9ph0j89wcna-bundler-2.1.4/lib/ruby/gems/2.7.0/gems/bundler-2.1.4/lib/bundler/rubygems_integration.rb:413:in `block in replace_bin_path'
/nix/store/ggqacj06n6qfm1iww0bih9ph0j89wcna-bundler-2.1.4/lib/ruby/gems/2.7.0/gems/bundler-2.1.4/lib/bundler/rubygems_integration.rb:374:in `block in replace_bin_path': can't find executable foreman for gem foreman. foreman is not currently included in the bundle, perhaps you meant to add it to your Gemfile? (Gem::Exception)
| 10:00:11 |
| das_j | Haven't seen that one before. Does it work when using the compat stuff (probably nix-shell) instead of nix develop? | 10:16:07 |
| niksnut | nix-shell gives the same error | 10:37:05 |
 lukegb (he/him) | Yeah, I can reproduce with that foreman storepath | 13:58:01 |
 cole-h | In reply to @niksnut:matrix.org
Anybody know what can cause this (running foreman in a nix develop shell):
$ foreman start
Warning: the running version of Bundler (2.1.4) is older than the version that created the lockfile (2.2.20). We suggest you to upgrade to the version that created the lockfile by running `gem install bundler:2.2.20`.
Traceback (most recent call last):
2: from /nix/store/ycshcdssxcj9sjf6yzb1ydw4fcglf66y-foreman-0.87.2/bin/foreman:20:in `<main>'
1: from /nix/store/ggqacj06n6qfm1iww0bih9ph0j89wcna-bundler-2.1.4/lib/ruby/gems/2.7.0/gems/bundler-2.1.4/lib/bundler/rubygems_integration.rb:413:in `block in replace_bin_path'
/nix/store/ggqacj06n6qfm1iww0bih9ph0j89wcna-bundler-2.1.4/lib/ruby/gems/2.7.0/gems/bundler-2.1.4/lib/bundler/rubygems_integration.rb:374:in `block in replace_bin_path': can't find executable foreman for gem foreman. foreman is not currently included in the bundle, perhaps you meant to add it to your Gemfile? (Gem::Exception)
The nixpkgs pinned in nixos/nix has a busted foreman. I looked into this before, one second -- lemme find the nixpkgs pr that fixed it. That's why I had to add a new nixpkgs input for my queue runner metrics PR | 14:37:16 |
| cole-h | https://github.com/NixOS/nixpkgs/pull/140391 | 14:37:47 |
 cransom | side tangent. i replaced all my foreman usage with goreman (a go re-implementation) and it has some nice extra features, like being able to-start individual services. i had some weirdness with tty handling and stdin with foreman and it uses the same procfile format. | 14:40:28 |
