-
Notifications
You must be signed in to change notification settings - Fork 25
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
PackagesNotFoundError listing more than missing package #447
Comments
This seems to be caused by https://github.com/conda/conda-libmamba-solver/blob/24.1.0/conda_libmamba_solver/solver.py#L376 https://github.com/mamba-org/mamba/blob/mamba-1.5.7/libmamba/src/core/solver.cpp#L38 With verbose logging on the 1st solve attempt I see
and on the 2nd attempt
If I add https://github.com/conda/conda-libmamba-solver/blob/24.1.0/conda_libmamba_solver/solver.py#L406 |
Looking at the comments added in this PR it seems like the order of when |
The problem is that the whatprovides relationships set in
I'll need to step through libmamba with gdb and verify this behavior |
Thanks for the detailed investigation! If there's a workaround we can add in Python, we can handle that here. If it has to be done in C++ land, then we'll need to contribute a patch to |
I think the change would have to be in the libmamba side unless we recreate a fresh pool instance for every solve attempt. I was able to confirm my previous comment by having |
Semi-related to this issue was that I noticed in the error messages that the channel pins would add duplicate entries
I created a PR for this #449 |
The issue is resolved in the mamba PR that's been merged so I'm closing this issue. |
I tried current 1.x locally and it works 🚀 Thanks! |
Checklist
What happened?
I'm unsure if this is a bug in
conda-libmamba-solver
orlibmamba
but in recent versions when trying to solve for a package missing in one channel it reports all requested packages as missing even if they're not.I'm able to reproduce it with the following:
Given this valid environment in
ok.yml
.conda env create --name ok --file ok.yml --dry-run
succeeds as expectedAfter copying the
ok.yml
file tobroken.yml
and changing one of these pins toconda-forge
conda env create --name broken --file broken.yml --dry-run
fails with the following error messageIn the past I would've seen something like this instead
Here's the issue reproduced in a github action build
https://github.com/tl-hbk/conda-solver-error-message/actions/runs/8190938627/job/22399027702
Conda Info
Conda Config
Conda list
Additional Context
No response
The text was updated successfully, but these errors were encountered: