| 16 Aug 2025 |
 emily | but where else are you going to hook up the Lix Pro billing flow | 14:15:58 |
 helle (just a stray cat girl) | you are describing exactly WHY I do not like have those logins that prominent | 14:17:00 |
| helle (just a stray cat girl) | :P | 14:17:03 |
| emily | the free tier is very generous – a whole 100 derivation builds per month (and those don't even count successful cache hits! you get 500 of those) | 14:17:25 |
| emily | more seriously, perhaps just adding quick links to the Gerrit top menu may be easy? | 14:18:02 |
 @aloisw:julia0815.de | Not to my knowledge, they are supposed to send it to you by email (that's where I got it from) but maybe that actually requires signing in once so that they can't be abused as a spam source. | 14:26:27 |
 -> @n:rab.lol | Okay now I'm back to square one - the failure just not being there on older nixpkgs. So naturally I'm bisecting nixpkgs now to see what changed | 21:36:44 |
| 17 Aug 2025 |
| -> @n:rab.lol | I had to take a break and I'm back to bisecting since now that I'm close to the offending change I have to skip 90% of the commits unless I wanted to rebuild the whole world. Does anyone have a script or something to only bisect over merge commits or only bisect over commits that had been built by hydra? That'd be invaluable as it always looks like this for me whenever I'm trying to bisect nixpkgs 😭 | 09:04:45 |
| @aloisw:julia0815.de | --first-parent is the usual recommendation to avoid going into staging. | 09:09:10 |
| -> @n:rab.lol | Yep that made it way better, thanks. Not sure why nobody mentions this option when googling for "bisect merge commits only" or whatever | 10:31:18 |
| -> @n:rab.lol | Of course the regression is at a staging merge that's so awesome, but at least I have my suspects now, let's see if I'm correct | 10:53:43 |
| -> @n:rab.lol | One of the regressions started happening after bumping bash, I don't know if I'm gonna update my config this weekend. I still have two other ones to identify | 11:34:03 |
| -> @n:rab.lol | Yeah so bash 5.3 breaks functional-user-envs, now I need to figure out why functional-remote-store and functional-nix-shell-basic started failing after that staging merge | 11:50:06 |
| helle (just a stray cat girl) | would it be in your skillset to move these to functional2? (this may depend on some f2 features not quite finished) | 12:30:22 |
