 | Nix Zürich | 115 Members |
| https://zurich.nix.ug/ - Next ZHF event 24-25 May 2025 | 27 Servers |
| Nix Zürich | 115 Members |
| https://zurich.nix.ug/ - Next ZHF event 24-25 May 2025 | 27 Servers |
| Sender | Message | Time |
|---|---|---|
| 15 Nov 2025 | ||
 zekjur | * in a current nixpkgs checkout, i modified frigate like so: https://paste.noname-ev.de/paste/113 and then i run nix build .#frigate, which ultimately prints something like: [1/0/1 built] building frigate-0.16.2 (pytestCheckPhase): sudo /nix/store/sikvbjrwks8hpbyglk76cn6iq3zvn0lp-attach/bin/attach 5167301 that’s what i run | 11:47:43 |
 kirelagin | ok, I see, I have never heard of this hook tbh. I usually just do nix devleop and then run phases manually. There used to be a wiki page explaining this (basically, how to troubleshoot failing builds with nix-shell but I can’t see to find it now :/) | 11:49:24 |
| zekjur | yeah the wiki page instructions never worked for me 🤷 maybe all my packages are unusual somehow :D | 11:49:47 |
| kirelagin | @zekjur anyway, what works for me is nix develop .#frigate, then, in the shell, you just do eval "${unpackPhase:-unpackPhase}", then the same with patchPhase, and then you, um, figure out what it does next, because the expression has dontBuild = true so I assume it just runs the tests or something. That’s the traditional way of debugging builds | 11:57:25 |
| kirelagin | * zekjur: anyway, what works for me is nix develop .#frigate, then, in the shell, you just do eval "${unpackPhase:-unpackPhase}", then the same with patchPhase, and then you, um, figure out what it does next, because the expression has dontBuild = true so I assume it just runs the tests or something. That’s the traditional way of debugging builds | 11:57:33 |
| kirelagin | * zekjur: anyway, what works for me is nix develop .#frigate, then, in the shell, you just do eval "${unpackPhase:-unpackPhase}", then cd in to the directory, then the same with patchPhase, and then you, um, figure out what it does next, because the expression has dontBuild = true so I assume it just runs the tests or something. That’s the traditional way of debugging builds | 11:57:58 |
| zekjur | thanks. let me try how far i get with the different phases | 12:04:28 |
| zekjur | running eval "${buildPhase:-buildPhase}" results in an entirely different error :( 2.009 × Failed to build installable wheels for some pyproject.toml based projects
| 12:05:58 |
| zekjur | okay, so the phase that fails is pytestCheckPhase, but when i run unpackPhase and pytestCheckPhase, i get a different error, too :-/ | 12:24:08 |
| kirelagin | Nix gives you reproducibility they say | 12:29:24 |
| kirelagin | Oh it segfaults lol | 12:31:19 |
| kirelagin | Yeah, the easy way to check is /nix/store/ab4v2qp7q426zrizz38d4jfx025xifdf-pytest-check-hook/nix-support/setup-hook: line 23: 541 Segmentation fault – if you look at that line, you’ll see it is the pytestCheckPhase | 12:32:01 |
| zekjur | ok, so this is failure is a known upstream issue (see https://github.com/blakeblackshear/frigate/discussions/20663), but not sure why i ran into that only this once -.- | 12:39:26 |
| zekjur | ok, i give up. there are too many unknowns for me (not familiar with python apps, frigate dev env instructions are very bare, nix debugging is a mystery) | 13:02:19 |
 raphiz | Mini-PRs Ready for review: https://github.com/NixOS/nixpkgs/pull/461902 | 13:06:46 |
 ners | Please vote if you haven't yet. | 13:06:47 |
| raphiz | PR ready for Review: https://github.com/NixOS/nixpkgs/pull/461918 | 13:17:37 |
 john-rodewald | In reply to @ners:nixos.devLooks like we’ll do it today. | 13:18:56 |
 Bryan Honof | https://www.neuhauschocolates.com/en_FI/home | 13:22:11 |
| kirelagin | zekjur: I’ve reproduced the failure:
| 13:33:02 |
| kirelagin | I’m not really sure what you are going to do with it though, because it is a segfault, so you will probably want to whip out gdb and then, um... get debug builds of CPython and all the packages involved that have C components? | 13:33:57 |
| kirelagin | Actually, you don’t even need to run any of the tests, just the collection (run pytest --co -q in the shell after going through all the phases) segfaults | 13:36:10 |
| zekjur | thank you! that gets me a core dump at least (after ulimit -c unlimited) :) | 13:38:14 |
| kirelagin | ok, actually, I am getting a meaningful stacktrace even with a regular build. It’s in the protobuf destruction, and the offending Python module is onnxruntime/capi/onnxruntime_pybind11_state.so | 13:38:30 |
| zekjur | yes. i’ll post the stack trace to the bug | 13:38:48 |
| zekjur | * yes. i’ll post the stack trace to the bug: https://github.com/NixOS/nixpkgs/issues/461064#issuecomment-3536499845 | 13:40:16 |
| zekjur | NixOS even already includes debug symbols for most involved packages :) i updated the stack trace with symbols. but mweinelt already commented saying the problem is multiple versions of protobuf in Nix, and it’s being addressed already | 13:43:46 |
| raphiz | PR ready for Review: https://github.com/NixOS/nixpkgs/pull/461924 | 13:52:29 |
 thomas-zahner | Package fixed: https://github.com/NixOS/nixpkgs/pull/461886 Now working on gerbera | 13:53:43 |
| ners | thomas-zahner: https://github.com/NixOS/nixpkgs/blob/8a8e49ac2069bc3de799a20016d7e6ae6853a503/pkgs/tools/security/pass/extensions/update.nix#L20 (but use --replace-fail) | 14:00:22 |