-
Notifications
You must be signed in to change notification settings - Fork 384
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
mamba failing with conda-build 3.26.0 #2715
Comments
This also seems to be failing for other conda commands with conda version 23.7.1 released last night:
|
Hmm we have a conda-canary build that tested with
4 days ago but maybe the change was in the meantime. |
Not seeing issues with conda 23.5.2, only with conda-build 3.26.0, conda 23.7.x or a combination of both |
Seems like it is also related to the issue |
This is actually an issue with
You can now see
|
I think #2732 should fix this |
…#522) * Initial work on making API endpoint for accessing role_mappings/metadat * Ruff checks * Major refactor to move towards explicit sessions in sqlalchemy * Getting celery tasks to use same database session * Disable thread check escape for proper testing * Black formatting * Remove echo statement * Fixing tests * Ensure that celery db is initialized and fix missing call * Do not check same thread in tests * Adding better debugging * Pinning conda version until 23.7.X issues are resolved See mamba-org/mamba#2715
Troubleshooting docs
How did you install Mamba?
Mambaforge
Search tried in issue tracker
conda build AttributeError
Latest version of Mamba
Tried in Conda?
I do not have this problem with Conda, just with Mamba
Describe your issue
As of conda-build 3.26.0
mamba build ~/conda_recipe
fails with the following error messageThis does not fail with conda-build 3.25.0 and
conda build ~/conda_recipe
andconda-build ~/conda_recipe
both succeed so there seems to be some broken interaction between mamba and conda/conda-build.mamba info / micromamba info
Logs
environment.yml
No response
~/.condarc
No response
The text was updated successfully, but these errors were encountered: