Excessive darwin sandbox entries can cause Apple's sandbox code to throw an assert #756
Labels
No labels
Affects/CppNix
Affects/Nightly
Affects/Only nightly
Affects/Stable
Area/build-packaging
Area/cli
Area/evaluator
Area/fetching
Area/flakes
Area/language
Area/lix ci
Area/nix-eval-jobs
Area/profiles
Area/protocol
Area/releng
Area/remote-builds
Area/repl
Area/repl/debugger
Area/store
bug
Context
contributors
Context
drive-by
Context
maintainers
Context
RFD
crash 💥
Cross Compilation
devx
docs
Downstream Dependents
E/easy
E/hard
E/help wanted
E/reproducible
E/requires rearchitecture
imported
Language/Bash
Language/C++
Language/NixLang
Language/Python
Language/Rust
Needs Langver
OS/Linux
OS/macOS
performance
regression
release-blocker
stability
Status
blocked
Status
invalid
Status
postponed
Status
wontfix
testing
testing/flakey
Topic/Large Scale Installations
ux
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-project/lix#756
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Test case:
Or: https://gerrit.lix.systems/c/lix/+/2870
This seems to only throw an assert when
NIX_STORE
is rebound to cause the paths to be much longer? idk. Gremlins.Weirdly enough this seems to also break when I
nix build --sandbox -f test.nix
even with the sandbox patch.cc #752
I have tried to create an independent repro but it doesn't work. idk what i am doing wrong that causes it to not have problems.
Well, whatever, here's a reproducer obtained by just extracting the profile from what Lix was putting in there, idk if it works on anyone else's machine, but it works on mine: https://gist.github.com/lf-/8ec3d714fd638873fe5324838c4dae4d#file-repro-md
Filed a bug (not convinced it will be fixed though): FB16964888
sandbox
setting is a horrifying field of landmines of implementation complexity #936