-
-
Notifications
You must be signed in to change notification settings - Fork 453
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segmentation fault #1291
Comments
I'm not getting a segmentation fault, but I can reliably get the following error with poetry2nix from this repository. The error goes away and the build succeeds if I use poetry2nix from nixpkgs.
|
I get this when I make poetry2nix follow nixpkgs/nixos-unstable, but not with nixpkgs/nixos-23.05 or the default version used by poetry2nix (without inputs.nixpkgs.follows). |
With the current rev of nixpkgs-unstable and poetry2nix I get:
when it runs long enough and it consumes about 16gig of memory before doing so |
I should maybe add that I have the following cofigured. echo "experimental-features = nix-command flakes" >> /etc/nix/nix.conf
echo "sandbox = false" >> /etc/nix/nix.conf
echo "filter-syscalls = false" >> /etc/nix/nix.conf |
I got it when trying to As said by @apeschar, everything works fine when using It's caused by NixOS/nixpkgs#248866 which switches to PyPA build, installer, and flit-core to build Python packages. The following commits are the root cause:
As our overrides only have the knowledge about old nixpkgs, it still think Nixpkgs has fixed this problem between these two commits, and there is actually a PR for us #1290 - although it has not merged yet when I'm writing this. Currently, the workaround includes using @K900's patch branch, using the poetry2nix from nixpkgs, or use a commit of nixpkgs prior to NixOS/nixpkgs#248866. |
#1290 is not actually a complete fix, there are still cases where it causes infinite recursion, and I'm pretty sure the correct way of doing it is to just rebuild everything with the nixpkgs bootstrap chain as-is, which would require more invasive changes to poetry2nix. |
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/how-to-troubleshoot-an-infinite-recursion-error/32565/5 |
I still have a segmentation fault using a patched branch. Any advice? https://github.com/vitvakatu/bleak-nix/blob/main/flake.nix |
As stated, not a complete fix. |
For me things started working when i reverted to quite the old version for poetry alone
The combination of K900's fix and using v22 solved it for me, using nixpkgs 23 introduced some python 3.11 issues |
For anyone searching for a commit from just before the break that is cached by Hydra, I initially tried By manually scrounging through Hydra's job logs, I think I've found 3476a10478587dec90acb14ec6bde0966c545cc0 run by Hydra in build 231993738 as our best bet for a cached build from before the break.
Edit: On a related note, does anyone know why this can even cause a segfault? Should that be its own bug on Nix? Maybe alongside some diagnostics for use in debugging infinite recursion, like Haskell has? |
This issue has been mentioned on NixOS Discourse. There might be relevant details there: |
This issue has been mentioned on NixOS Discourse. There might be relevant details there: |
Nixpkgs Python now has a small separate set with bootstrapping packages along with new hooks replacing Bootstrapping for the Python core packages had to be changed because packages also started using different build systems. I think it is probably better for |
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/nix-shell-is-eating-up-all-my-32-gb-memory/34134/2 |
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/function-anonymous-lambda-called-with-unexpected-argument/34267/2 |
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/function-anonymous-lambda-called-with-unexpected-argument/34267/3 |
The pyk update job in evm semantics is currently failing due to mismatch with nixpkgs. The latest version of poetry2nix lets us choose which nixpkgs get used to build poetry packages, by introducing `mkPoetry2Nix { pkgs = <my nixpkgs version here>; })`. This will allow us to use a separate version of nixpkgs to build pyk vs the rest of k-framework, at least until at least the time nixpkgs stable catches up with changes described here: nix-community/poetry2nix#1291. However, we may always want to use a custom version of nixpkgs for poetry projects downstream, pinned to the version here. This should ensure that if pyk builds in this repository, it will also build in all the downstream projects which use it. --------- Co-authored-by: devops <[email protected]>
The pyk update job in evm semantics is currently failing due to mismatch with nixpkgs. The latest version of poetry2nix lets us choose which nixpkgs get used to build poetry packages, by introducing `mkPoetry2Nix { pkgs = <my nixpkgs version here>; })`. This will allow us to use a separate version of nixpkgs to build pyk vs the rest of k-framework, at least until at least the time nixpkgs stable catches up with changes described here: nix-community/poetry2nix#1291. However, we may always want to use a custom version of nixpkgs for poetry projects downstream, pinned to the version here. This should ensure that if pyk builds in this repository, it will also build in all the downstream projects which use it. --------- Co-authored-by: devops <[email protected]>
The pyk update job in evm semantics is currently failing due to mismatch with nixpkgs. The latest version of poetry2nix lets us choose which nixpkgs get used to build poetry packages, by introducing `mkPoetry2Nix { pkgs = <my nixpkgs version here>; })`. This will allow us to use a separate version of nixpkgs to build pyk vs the rest of k-framework, at least until at least the time nixpkgs stable catches up with changes described here: nix-community/poetry2nix#1291. However, we may always want to use a custom version of nixpkgs for poetry projects downstream, pinned to the version here. This should ensure that if pyk builds in this repository, it will also build in all the downstream projects which use it. --------- Co-authored-by: devops <[email protected]>
The pyk update job in evm semantics is currently failing due to mismatch with nixpkgs. The latest version of poetry2nix lets us choose which nixpkgs get used to build poetry packages, by introducing `mkPoetry2Nix { pkgs = <my nixpkgs version here>; })`. This will allow us to use a separate version of nixpkgs to build pyk vs the rest of k-framework, at least until at least the time nixpkgs stable catches up with changes described here: nix-community/poetry2nix#1291. However, we may always want to use a custom version of nixpkgs for poetry projects downstream, pinned to the version here. This should ensure that if pyk builds in this repository, it will also build in all the downstream projects which use it. --------- Co-authored-by: devops <[email protected]>
The pyk update job in evm semantics is currently failing due to mismatch with nixpkgs. The latest version of poetry2nix lets us choose which nixpkgs get used to build poetry packages, by introducing `mkPoetry2Nix { pkgs = <my nixpkgs version here>; })`. This will allow us to use a separate version of nixpkgs to build pyk vs the rest of k-framework, at least until at least the time nixpkgs stable catches up with changes described here: nix-community/poetry2nix#1291. However, we may always want to use a custom version of nixpkgs for poetry projects downstream, pinned to the version here. This should ensure that if pyk builds in this repository, it will also build in all the downstream projects which use it. --------- Co-authored-by: devops <[email protected]>
The pyk update job in evm semantics is currently failing due to mismatch with nixpkgs. The latest version of poetry2nix lets us choose which nixpkgs get used to build poetry packages, by introducing `mkPoetry2Nix { pkgs = <my nixpkgs version here>; })`. This will allow us to use a separate version of nixpkgs to build pyk vs the rest of k-framework, at least until at least the time nixpkgs stable catches up with changes described here: nix-community/poetry2nix#1291. However, we may always want to use a custom version of nixpkgs for poetry projects downstream, pinned to the version here. This should ensure that if pyk builds in this repository, it will also build in all the downstream projects which use it. --------- Co-authored-by: devops <[email protected]>
Describe the issue
Running
nix build
ornix flake check
causes a segmentation fault.Additional context
Tried on the following machines.
default.nix
/shell.nix
/flake.nix
:flake.lock
:pyproject.toml
:poetry.lock
The text was updated successfully, but these errors were encountered: