Replies: 6 comments 2 replies
-
Hi @gzt5142, thanks for bringing this to our attention. I haven't run into this issue before and from looking at the |
Beta Was this translation helpful? Give feedback.
-
Hi... other environments do not raise this error:
|
Beta Was this translation helpful? Give feedback.
-
behavior has evolved:
Is this likely to do with how this particular environment has been created/configured on our host? |
Beta Was this translation helpful? Give feedback.
-
admin is not among the namespaces where I can create environments. Have re-built an environment in a
The environment def that I am using:
The YML generated in conda-store is attached. |
Beta Was this translation helpful? Give feedback.
-
I'm seeing this same behavior. Its throwing this error even when activating the default environment:
However, I haven't seen it actually break anything - my env still activates and I can run stuff in python (so far) without issue. |
Beta Was this translation helpful? Give feedback.
-
I've opened an issue to track this, let's move further discussion over there. @gzt5142 thanks for opening this discussion up! Feel free to add additional info to the issue :) |
Beta Was this translation helpful? Give feedback.
-
Unable to activate an existing environment created in the user space.
An environment listed when I
conda env list
raises an error when I attempt to activate it:This error does not seem to impact the environment -- it appears to activate -- but this
mkdir
error is new behavior suggesting a failure of some kind. I would like to understand the implications of the failure/error.Beta Was this translation helpful? Give feedback.
All reactions