-
Notifications
You must be signed in to change notification settings - Fork 104
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
Ensure that the mamba/conda version being used is not too old #577
Comments
Thanks for the report! I have been unable to reproduce this issue locally. I suspect it could have to do with the Conda executable. Unfortunately the stack trace doesn't provide me with enough info to understand what's going on. (We should improve this.) Could you please edit print_proc(proc) This should let us figure out what's going on. |
That helps a lot! Here's what we gained:
Something seems screwed up with Mamba. Could you please try running:
I hope it's an old Mamba version, and upgrading Mamba will fix the issue. Note to self: we should check the version of Mamba before using it, and encourage the user to upgrade in case they're using something ancient. |
Ok great;
I'm far from being an expert with Python environments so I wouldn't be surprised if |
So I have updated mamba via conda using And now doing It could have been nice to have some checks on the version of mamba indeed, but thanks a lot for your help @maresb! |
Thanks for taking the time to make the report @r-molins-mrp. Also I'm glad I could fix your problem. I'll rework this issue into a todo... |
Previous title: conda-lock -f environment.yml returns JSONDecodeError and fails
Checklist
What happened?
When trying to run
conda-lock -f environment.yml
with the following
environment.yml
file:it returns:
And fails - the lock file is not created.
Conda Info
Conda Config
Conda list
Additional Context
No response
The text was updated successfully, but these errors were encountered: