Nix Hackers | 951 Members | |
| For people hacking on the Nix package manager itself | 196 Servers |
| Sender | Message | Time |
|---|---|---|
| 4 Dec 2024 | ||
| * Well now the manual seems to point to nix 2.24. | 07:04:30 | |
| 22:49:41 | ||
| 5 Dec 2024 | ||
| 17:36:54 | ||
| Hi Arian! You probably got to the bottom of this problem by now, right? For the future though, I just added this S3 logging change to Nix: https://github.com/NixOS/nix/pull/12007 This will print an ID which you can use to find more information in CloudWatch. | 19:09:19 | |
| 20:38:27 | ||
| 20:38:47 | ||
| 6 Dec 2024 | ||
| 03:43:51 | ||
| Perhaps we should adopt the "oldstable" name? I've seen that name pop up during the support window overlap before | 13:59:55 | |
| I just hit what looks like this old issue: https://github.com/NixOS/nixpkgs/issues/138157
| 14:40:03 | |
| * I just hit what looks like this old issue: https://github.com/NixOS/nixpkgs/issues/138157
| 14:40:52 | |
| * I just hit what looks like this old issue: https://github.com/NixOS/nixpkgs/issues/138157
| 14:41:23 | |
| I see a handful of issues of this style open against nix as well. https://github.com/NixOS/nix/issues?q=is%3Aissue+json+json.exception.parse_error+is%3Aopen Is this a recently introduced stdenv issue | 14:44:37 | |
| p14: https://github.com/NixOS/nix/pull/11921 | 15:53:27 | |
| This is while running 'nix develop' though, there is no indication of any build taking place | 15:54:37 | |
| * This is while running 'nix develop' on any package in staging though, there is no indication of any build taking place | 15:54:55 | |
| p14: I have the feeling if all packages are doing that, we should also fix this in nixpkgs. It should not echo invalid json | 16:11:30 | |
| Do you know what change introduces this? | 16:11:46 | |
In reply to @joerg:thalheim.ioI do not, sorry, my time budget blew and I am now afk for a bit. Seems master is ok but not staging. | 16:16:50 | |
| Maybe give a heads up in the staging channel at least. | 16:17:23 | |
| The pull request is only improving the error message, but not fixing the root cause, which is on the nixpkgs side. | 16:17:55 | |
| I believe I have once fixed illegal utf8 logs, it is not correct to skip those lines entirely: https://github.com/NixOS/nix/pull/5160 | 17:46:50 | |
| There would always be those errors on nixpkgs side, because builder scripts aren't forced to output utf8-only logs, yet nix is converting those logs to json, and json library only expects utf8 strings | 17:50:02 | |
| 7 Dec 2024 | ||
| Is it even possible to use garbage collection with a diverted store? No matter what I do, gc roots get created as /nix/store symlinks and the garbage collector deletes out of /nix/store | 03:47:06 | |
| 16:59:55 | ||
| 20:58:08 | ||
| 8 Dec 2024 | ||
| 09:35:00 | ||
| That feels like a bug. | 20:10:19 | |
| 9 Dec 2024 | ||
| Lach: isn't json supposed to be either unicode or ascii with escaped chars? | 12:16:33 | |
| Ascii with escaped chars shouldn't include invalid unicode sequences (Unpaired surrogates are allowed at max), yet builder scripts might output invalid unicode sequences, and nix worker protocol requires this output to be encoded to json, which is impossible in general, invalid utf-8 sequences must be replaced | 12:48:07 | |
| 10 Dec 2024 | ||
| 15:24:22 | ||