-
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
KeyError after possible bad replacing when using conda-lock #230
Comments
We are also experiencing this issue. |
Are you also using
|
Also note conda-lock has 2.1.1 now and that's the one I used for my tests. |
Sorry about the noise, I can indeed reproduce. I hadn't enabled the solver 🤦. Checking now! |
I now think that this could be a conda-lock issue. The command that is failing involves a temporary directory input. That temporary directory is deleted when conda-lock exits making it difficult to check it isn't the source of the problem. If one omits the temporary directory from the conda command then the command completes successfully. If one copies the temporary directory while it is running via conda-lock, and then copies it back after it is deleted, then re-run the internal conda command directly referencing the temporary directory, then the problem re-surfaces. This suggests to me it is the contents of that temporary directory that cause conda to fail and I am assuming that temporary directory is created by conda-lock. I am using conda 23.5.2, conda-lock 2.1.0, conda-libmamba-solver 23.5.0, libmamba 1.4.9, and libmambapy 1.4.9. |
I looked into it a bit more and it's about the injected virtual packages via |
Checklist
What happened?
I'm not 100% sure this issue is right on this tracker given that I only experience it when using
conda-lock
. However, from the traceback I'm getting, it looks likeconda-lock
does the right thing. Furthermore, this error does not pop up when disabling thelibmamba
solver.Imagine I have an environment like
The interesting part is "hidden" behind the "traceback" key:
This seems like a bad replacement: it is looking for
https://conda.anaconda.org/@/linux-64
whilehttps://conda.anaconda.org/conda-forge/linux-64
is available. However, the command executed byconda-lock
seems to be fine:This is why I'm reporting here rather than
conda-lock
. I have looked through that tracker as well, but didn't find an issue for this there either.While debugging this, I found that this is not always happening. For example
works fine.
panel
in the original environment is however not the culprit. All other packages than plainpython
did not work for me.Conda Info
Conda Config
Conda list
Additional Context
The text was updated successfully, but these errors were encountered: