prefix-dev
Installation hanging on `downloading repodata`
Reproducible example
The problem with this is that I've yet to find a way to reproduce the issue. The only noteworthy resemblance between the cases this happens to me is that:
- Installing a large set of packages, often ROS environments or similarly large set of dependencies.
- Installing from multiple channels seems to have something to do with it.
- Clean or Full cache doesn't seem to make a difference.
- I can often reproduce it multiple times after another, until the stars ⭐ misalign again, and I can't figure out how to reproduce it anymore.
The result looks something like this in a terminal:
The longest I've left it running was at least 5 minutes, but that doesn't seem to matter. I've not seen it happen on Sharded repodata and going into debug it often spends a lot of time in the JLAP code but I've been able to pin point it any further, so this is just an idea right now.
Expected behavior
Not getting stuck on downloading repodata.
This just happened to me and the only thing I did was:
pixi init --format pyproject pixi add pixi-pycharm
I was on 0.42.1 but upgrading to 0.44.0 didn't fix it.
Macos Sequoia 15.3.2 on an old Intel MBP.
I tried inside the Pycharm terminal and also in Iterm2, it makes no difference.
While I was typing this I just let it run and after ~5 minutes I got:
% pixi add python pixi-pycharm
Error: × Request failed after 3 retries
├─▶ error sending request for url (https://conda.anaconda.org/conda-forge/noarch/repodata_shards.msgpack.zst)
├─▶ client error (Connect)
├─▶ tcp connect error: Operation timed out (os error 60)
╰─▶ Operation timed out (os error 60)
So I tried pypi but also that didn't help:
% pixi add python pixi-pycharm --pypi
By the way in my case it happens every single time. I'm unable to use pixi right now, had to switch to another tool to manage my env.
Just ran into this. I'm running on a Debian 12 machine (using Pixi 0.48.1), and it always succeeds resolving linux-64 and osx-arm64, but always hangs indefinitely when osx-64 and/or win-64 are listed as platforms.
$ pixi add numpy -v
INFO pixi_manifest::discovery: Found manifest in directory: "/home/boylec0/projects/delete_me", continuing further.
INFO pixi_manifest::pyproject: Overriding the requires-python with the one defined in pixi dependencies
INFO pixi::environment: verifying prefix location is unchanged, with prefix file: /home/boylec0/projects/delete_me/.pixi/envs/conda-meta/pixi_env_prefix
INFO pixi::lock_file::outdated: the dependencies of environment 'default' for platform osx-arm64 are out of date because the requirement 'numpy *' could not be satisfied (required by '<environment>')
INFO pixi::lock_file::outdated: the dependencies of environment 'default' for platform linux-64 are out of date because the requirement 'numpy *' could not be satisfied (required by '<environment>')
INFO pixi::lock_file::outdated: the dependencies of environment 'default' for platform win-64 are out of date because missing purls
INFO pixi::lock_file::outdated: the dependencies of environment 'default' for platform osx-64 are out of date because missing purls
INFO pixi::lock_file::outdated: the dependencies of environment 'dev' for platform osx-64 are out of date because missing purls
INFO pixi::lock_file::outdated: the dependencies of environment 'dev' for platform linux-64 are out of date because the requirement 'numpy *' could not be satisfied (required by '<environment>')
INFO pixi::lock_file::outdated: the dependencies of environment 'dev' for platform win-64 are out of date because missing purls
INFO pixi::lock_file::outdated: the dependencies of environment 'dev' for platform osx-arm64 are out of date because the requirement 'numpy *' could not be satisfied (required by '<environment>')
INFO pixi::lock_file::outdated: the dependencies of environment 'py311' for platform win-64 are out of date because missing purls
INFO pixi::lock_file::outdated: the dependencies of environment 'py311' for platform linux-64 are out of date because the requirement 'numpy *' could not be satisfied (required by '<environment>')
INFO pixi::lock_file::outdated: the dependencies of environment 'py311' for platform osx-64 are out of date because missing purls
INFO pixi::lock_file::outdated: the dependencies of environment 'py311' for platform osx-arm64 are out of date because the requirement 'numpy *' could not be satisfied (required by '<environment>')
INFO pixi::lock_file::outdated: the dependencies of environment 'py312' for platform linux-64 are out of date because the requirement 'numpy *' could not be satisfied (required by '<environment>')
INFO pixi::lock_file::outdated: the dependencies of environment 'py312' for platform osx-arm64 are out of date because the requirement 'numpy *' could not be satisfied (required by '<environment>')
INFO pixi::lock_file::outdated: the dependencies of environment 'py312' for platform osx-64 are out of date because missing purls
INFO pixi::lock_file::outdated: the dependencies of environment 'py312' for platform win-64 are out of date because missing purls
INFO pixi::lock_file::outdated: the dependencies of environment 'py313' for platform osx-64 are out of date because missing purls
INFO pixi::lock_file::outdated: the dependencies of environment 'py313' for platform win-64 are out of date because missing purls
INFO pixi::lock_file::outdated: the dependencies of environment 'py313' for platform linux-64 are out of date because the requirement 'numpy *' could not be satisfied (required by '<environment>')
INFO pixi::lock_file::outdated: the dependencies of environment 'py313' for platform osx-arm64 are out of date because the requirement 'numpy *' could not be satisfied (required by '<environment>')
INFO pixi::lock_file::resolve::uv_resolution_context: uv keyring provider is disabled
INFO resolve_conda{group=py313 platform=osx-arm64}: pixi::lock_file::update: fetched 42856 records in 737.568041ms
INFO resolve_conda{group=default platform=osx-arm64}: pixi::lock_file::update: fetched 42856 records in 740.379016ms
INFO resolve_conda{group=py312 platform=osx-arm64}: pixi::lock_file::update: fetched 42856 records in 741.797089ms
INFO resolve_conda{group=py311 platform=osx-arm64}: pixi::lock_file::update: fetched 42856 records in 746.024298ms
INFO resolve_conda{group=py313 platform=linux-64}: pixi::lock_file::update: fetched 93942 records in 1.59788696s
INFO resolve_conda{group=py312 platform=linux-64}: pixi::lock_file::update: fetched 93942 records in 1.597950742s
INFO resolve_conda{group=py311 platform=linux-64}: pixi::lock_file::update: fetched 93942 records in 1.607031142s
INFO resolve_conda{group=default platform=linux-64}: pixi::lock_file::update: fetched 93942 records in 1.61357854s
INFO pixi::lock_file::update: resolved conda environment for environment 'py312' 'osx-arm64' in 9s 687ms 256us 213ns
INFO pixi::lock_file::update: resolved conda environment for environment 'py313' 'osx-arm64' in 9s 687ms 665us 61ns
INFO pixi::lock_file::update: resolved conda environment for environment 'py311' 'osx-arm64' in 9s 690ms 646us 113ns
INFO pixi::lock_file::update: resolved conda environment for solve group 'default' 'osx-arm64' in 9s 688ms 123us 1ns
INFO pixi::lock_file::update: resolved conda environment for environment 'py312' 'linux-64' in 17s 93ms 526us 71ns
INFO pixi::lock_file::update: resolved conda environment for environment 'py313' 'linux-64' in 17s 93ms 415us 940ns
INFO pixi::lock_file::update: resolved conda environment for solve group 'default' 'linux-64' in 17s 114ms 259us 805ns
INFO pixi::lock_file::update: resolved conda environment for environment 'py311' 'linux-64' in 17s 244ms 110us 59ns
⠤ updating lock-file [00:14:33] [━━━━━━╾─────────────────────────────────] 8/52
⠈ py311:osx-64 [00:14:33] [━━━━━━━━━━━━━━━━━━━━] 0 B @ 0 B/s downloading repodata
⠈ py311:win-64 [00:14:33] loading repodata
⠈ default:osx-64 [00:14:33] loading repodata
⠈ py312:osx-64 [00:14:33] loading repodata
⠈ py312:win-64 [00:14:33] loading repodata
⠈ py313:osx-64 [00:14:33] loading repodata
⠈ py313:win-64 [00:14:33] [━━━━━━━━━━━━━━━━━━━━] 0 B @ 0 B/s downloading repodata
⠈ default:win-64 [00:14:33] loading repodata
(reducing the number of environments/features does not seem to affect anything)
It happens to me occasionally, I have to manually clean repodata cache every time it get stuck. FYI I am working in an HPC environment where my project data and home directory (where all the caches reside) are mounted on two network-based file systems, one using Lustre and the other using NFS.
