Nix Hackers | 908 Members | |
| For people hacking on the Nix package manager itself | 189 Servers |
| Sender | Message | Time |
|---|---|---|
| 14 Nov 2024 | ||
I’d like to add functionality to nix derivation show so it respects —keep-going. How would I do that?I found the relevant source file (https://github.com/NixOS/nix/blob/a95f6ea5c6b9a404f3ef1138c8351f7ef6383e6f/src/nix/derivation-show.cc#L42) and started by wrapping things in try-catch blocks, but I don’t understand how to catch the relevant errors — they seem to make the program fail regardless of what I’m catching ( EvalError, Error, or even std::exception).Does EvalState need to be reset or otherwise modified to start doing evaluation again after throwing?Will post changes in a moment. | 16:56:28 | |
| For what it's worth, even with the code below I'm not seeing anything being printed out, which I would expect due to the numerous
| 17:30:17 | |
| Ugh. Because I'm using a multi-user install, is it the daemon which is throwing the error? | 17:44:12 | |
toDerivations throws the eval exceptions, iirc | 17:50:06 | |
| That was it! Thank you :) | 18:55:04 | |
| 21:09:09 | ||
| 15 Nov 2024 | ||
| 12:36:24 | ||
| Yesterday I got an error in a Nix build which was using Ninja (nothing new there, bad CMake config). However, I noticed I was able to reliably reproduce a Nix error: https://gist.github.com/ConnorBaker/5cebac5224ab430e67ee25d7a5bd0224
Any idea if there's a limit on the length of the output from a build? I believe this was using a remote builder if that's any help. | 18:04:25 | |
In reply to @connorbaker:matrix.orgI wonder what --log-format internal-json will show? | 18:41:36 | |
Running it again with that flag. For what it's worth, when I built locally and used sudo (so no daemon) I didn't get the error. | 19:24:41 | |
| * Running it again with that flag. For what it's worth, when I built locally and used
| 19:25:05 | |
Here's the end of the log with --log-format internal-json https://gist.github.com/ConnorBaker/6af002385527635deefdce7982d2acb1 | 19:31:08 | |
| * Running it again with that flag. For what it's worth, when I built locally and used
| 19:31:58 | |
Weird that in the internal-json log output I can see \nFor full logs, run '\u001b[1mnix log /nix/store/w9nxvfann68v2am1kym3hkyxmc4a8p1f-cuda12.6-onnxruntime-1.20.0-unstable-2024-11-14.drv, but that in the log immediately above that output never shows up. | 19:32:36 | |
| 16 Nov 2024 | ||
| 10:47:55 | ||
In reply to @mightyiam:matrix.orgIt did some light digging in lldb here, but wasn't able to get to the root cause. https://github.com/NixOS/nix/issues/11286#issuecomment-2398006754. It's a use-after-free | 10:53:48 | |
| 18:22:43 | ||
| 18 Nov 2024 | ||
| 08:03:09 | ||
| https://github.com/NixOS/nixpkgs/pull/356983 fix darwin nix static build | 15:11:38 | |
| 16:27:06 | ||
| 19:36:58 | ||
| 19 Nov 2024 | ||
In reply to @connorbaker:matrix.orgwe have fixed this bug in lix | 08:51:37 | |
it clumsily parses anything that says @nix in the output as json, which is used for setPhase inside stdenv that shows the phase in the progress bar, like, unpackPhase, etc | 08:52:48 | |
| this used to cause the entire build to fail | 08:53:07 | |
| https://gerrit.lix.systems/c/lix/+/2057 probably | 08:53:43 | |
| got this for the first time today
| 16:22:34 | |
| Hi. Wanted to share a pretty curious finding. I've been looking into speeding up the flex generated lexer by using the full scanner tables I've run into a funny issue, which really looks like either a
Looks like the generated scanner trips up lots of other cases with comments as well. Has anyone else previously looked into using full scanners previously? | 22:37:43 | |
| * Hi. Wanted to share a pretty curious finding. I've been looking into speeding up the flex generated lexer by using the full scanner tables I've run into a funny issue, which really looks like either a
Looks like the generated scanner trips up lots of other cases with comments as well. Has anyone else previously looked into using full scanners? | 22:43:58 | |
| 20 Nov 2024 | ||
| 00:59:23 | ||
| 01:39:00 | ||