-
Notifications
You must be signed in to change notification settings - Fork 180
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
Too many open files #1551
Comments
While I agree that this can be a problem other package managers also frequently run into it (e.g. Yarn). We could try to figure out the current |
Maybe an easier workaround would be to improve the error message. Maybe you can globally hardcode something like
|
I'm not getting this regularly even with small environments |
Do you mean "are getting this regularly"? |
I meant
|
Mm, we do have some code in place to ensure we don't perform too many IO requests. Do you always get the error |
macOS default: 256 I was unable to reproduce just now. I'll post the error messages when it happens again |
Got it again:
|
I have the same ulimit, but don't see this error often. Your environment does look pretty big though (569 packages). I wonder if we could defend against this and react on the specific "too many open files" error by waiting, and retrying a few milliseconds later. |
I also get this error with 0.27.0 on MacOS with default
Followed this guide: https://holoviz-dev.github.io/panel/developer_guide/index.html And get this error:
Would be great if you could improve pixi to make this work with defaults on MacOS. Anyone knows what the workaround is? With Google I find various commands to change system settings for older versions of MacOS but usually with comments that they don't work reliably or are not recommended. |
|
There is an open PR by @baszalmstra - I need to test it though. |
Bas' PR works for me on macOS so I think we can merge and it'll be in the next release :) |
@wolfv @baszalmstra I'm still seeing this on Apple silicon macOS on v0.28.2 with ~ % pixi self-update
✔ pixi is already up-to-date (version 0.28.2)
~ % pixi global upgrade-all
× failed to parse '/Users/feickert/.pixi/envs/uv/conda-meta/uv-0.4.2-hd3a8144_0.json'
╰─▶ Too many open files (os error 24)
~ % ulimit -n
256
~ % ulimit -n 2048
~ % pixi global upgrade-all
Nothing to upgrade This is happening with a decently large pixi global list:~ % pixi global list
Global install location: /Users/feickert/.pixi
├── anaconda-client 1.12.3
| └─ exec: conda-server, anaconda, binstar
├── asciinema 2.4.0
| └─ exec: asciinema
├── bat 0.24.0
| └─ exec: bat
├── cmake 3.30.3
| └─ exec: cmake, ctest, cpack, ccmake
├── cookiecutter 2.6.0
| └─ exec: cookiecutter
├── crane 0.20.2
| └─ exec: crane
├── curl 8.9.1
| └─ exec: curl
├── git 2.46.0
| └─ exec: scalar, git-upload-pack, git-shell, git, git-cvsserver, git-credential-osxkeychain, git-upload-archive, gitk, git-receive-pack
├── grayskull 2.7.1
| └─ exec: conda-grayskull, conda-greyskull, grayskull, greyskull
├── hepconvert 1.3.7
| └─ exec: hepconvert
├── hyperfine 1.18.0
| └─ exec: hyperfine
├── jupyter-repo2docker 2024.7.0
| └─ exec: repo2docker, jupyter-repo2docker
├── lhapdf 6.5.4
| └─ exec: lhapdf, lhapdf-config
├── miller 6.12.0
| └─ exec: mlr
├── ninja 1.12.1
| └─ exec: ninja
├── pandoc 3.3
| └─ exec: pandoc-server, pandoc, pandoc-lua
├── pipx 1.7.1
| └─ exec: pipx
├── pre-commit 3.8.0
| └─ exec: pre-commit
├── pytube 15.0.0
| └─ exec: pytube
├── rattler-build 0.20.0
| └─ exec: rattler-build
├── ruff 0.6.2
| └─ exec: ruff
├── shellcheck 0.10.0
| └─ exec: shellcheck
├── tree 2.1.3
| └─ exec: tree
├── uproot-browser 0.6.7
| └─ exec: uproot-browser
├── uv 0.4.2
| └─ exec: uvx, uv
├── visidata 2.11
| └─ exec: vd, visidata
└── xrootd 5.7.0
└─ exec: frm_admin, frm_xfragent, xrdcopy, xrdmapc, xrdcrc32c, xrdgsiproxy, xrdpinls, xrdpwdadmin, xrdreplay, wait41, xrootd, xrdcks, xrdcp, xrdpfc_print, xrdfs, mpxstats, xrdacctest, xrdgsitest, xrdsssadmin, xrootd-config, cmsd, frm_xfrd, frm_purged, cconfig, xrdadler32 I'm not sure how much of this is a shortcoming of macOS defaults vs. something that is fixable on the software side. |
Do you see anything related to r limit in the logs when you run it with -v ? If not would you be able to open a new issue? This may be related to the upgrade-all subcommand. |
@baszalmstra I'm not always able to reproduce it — it seems to come and go. I'll be away from the Apple silicon macOS machine this week but I'll try to get a consistent reproducer and make a new issue if needed. |
Much appreciated! I will double check the code in the meantime. |
I get this error with pixi 0.28.2 now:
|
I've opened Issue #2005 for this now. 👍 |
Checks
I have checked that this issue has not already been reported.
I have confirmed this bug exists on the latest version of pixi, using
pixi --version
.Reproducible example
Issue description
Running a large new environment for the first time, on macOS:
Expected behavior
Should do fewer things in parallel so as to not go over macOS
ulimit -n
The text was updated successfully, but these errors were encountered: