Skip to content
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

Reinstallation might skip the use of the package cache #2667

Closed
2 tasks done
ruben-arts opened this issue Dec 9, 2024 · 1 comment · Fixed by #2700
Closed
2 tasks done

Reinstallation might skip the use of the package cache #2667

ruben-arts opened this issue Dec 9, 2024 · 1 comment · Fixed by #2700
Assignees

Comments

@ruben-arts
Copy link
Contributor

ruben-arts commented Dec 9, 2024

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

When installing a project with pypi dependencies the python build environments need to be installed using conda. I found that the installation might be slow because it doesn't always use the cache for all the packages that it needs.

I could reproduce it on https://github.com/sklearn-compat/sklearn-compat.

# Install once to fill the package cache, because by default it's not satisfied it will also install the build envs.
> pixi install
# Clean the environments to force a reinstallation
> pixi clean
# Change a single thing in the `pyproject.toml` to force a resolve of the pypi dependencies
> pixi project version set 1.2.3

# Test the solve again
> pixi install -v 
# This takes minutes on my machine because it starts downloading SOME packages which is non deterministic

Expected behavior

Environment installations should always use the cache when it was already installed before.

@baszalmstra
Copy link
Contributor

Fixed by conda/rattler#977

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants