Fix mamba not writable cache error#1108
Merged
Merged
Conversation
Member
Author
|
@wolfv any idea why the tests you introduced recently are failing on Windows? Will try to debug that if you don't have time to have a look. |
Member
Author
|
The exact same tests are failing on |
use first writable cache dir in Channel ctor
875f23b to
2b629b5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Fix
mambaruntime_errorwhenroot_prefixcache in not writableUse the first writable cache dir in
Channelconstructor to re-useContext.pkgs_dirsfilled usingcondaapiThe bug has been introduced in #1033, by using
libmambaChannelinstead ofconda's one.Closes #1098