If an environment has NO successful builds, then a Failed build is listed as Active. Obviously if the build failed, there is no environment to be active.
Note that the env does NOT appear in the list of available kernels when selecting an env from a jupyter notebook so that functionality is correct.
Expected behavior
If an environment has never successfully build, I expect there to be no Active env
Describe the bug
If an environment has NO successful builds, then a
Failed
build is listed asActive
. Obviously if the build failed, there is no environment to be active.Note that the env does NOT appear in the list of available kernels when selecting an env from a jupyter notebook so that functionality is correct.
Expected behavior
If an environment has never successfully build, I expect there to be no Active env
How to Reproduce the problem?
Output
No response
Versions and dependencies used.
No response
Anything else?
Separate issue also surrounding the Failed envs: https://github.com/conda-incubator/conda-store-ui/issues/248