Matthew Kenigsberg
Matthew Kenigsberg
As discussion has stalled out and this breaks `containerize`: > Realised that this breaks flox containerize which uses --accept-flake-config as root within a container and isn't affected by the default...
We can close this after using a Nix-provided `sleep`
Saw this again in https://github.com/flox/flox/actions/runs/10390132193/job/28770507812?pr=1920#step:6:410
> Shouldn't the fixup stage of a nix-build catch this? I really wish software always did what it should
> Shouldn't the fixup stage of a nix-build catch this? But yeah not sure why it's not. The debug logs have ``` 2024-07-23T17:39:32.390733Z DEBUG flox_rust_sdk::providers::git: running git command: /nix/store/hkkkpxwdcnfk6jwld8968vbz475jhcaw-git-minimal-2.42.0/bin/git -c...
If you have git installed and export `GIT_PKG=$(which git)`, does that workaround it?
I'm wondering if this might actually be a glibc bug not a jemalloc bug? It seems like the combination of TLS usage in LD_PRELOAD with LD_AUDIT causes the failure. Looking...
> Is there any limit on TLS size? If not it seems like this may be a glibc bug? I went ahead and created a glibc bug https://sourceware.org/bugzilla/show_bug.cgi?id=31991
If you activate with `--mode run`, do you end up with Python 3.10?
You can install Python modules with Flox, but in order for Python to find them, PYTHONPATH needs to get updated to point at .flox/run/aarch64-darwin.ftest.dev/lib/python3.12/site-packages. PYTHONPATH is one of the environment...