-
Notifications
You must be signed in to change notification settings - Fork 294
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
List of kernels shows deleted non-existent conda environments #6164
Comments
@elkir thanks for the bug. Please could you update your installed copies of the Jupyter and Python extensions for VS Code? We have made several improvements to conda kernel handling in both, and those may resolve the scenario you are reporting. Thank you! |
Jupyter v2021.5.745244803 The Python: Select interpreter works fine. It's only the Jupyter version that has the deleted ones. |
Thanks |
Here is the file:
|
This works as expected if you reload twice after deleting the env (instead of just once). I'm looking into why |
This is an issue with getInterpreters() in the python api. Version: 1.57.0-insider (user setup) Python extension version: v2021.5.842923320 Steps to reproduce
It also reproduces in reverse
|
Moving this back,
as mentioned above by the user its a problem in Jupyter (Python doesnt display the deleted items) |
@DavidKutu if you thinnk there's a Python extension issue as well, please create a new issue (this way we fix both bugs, the one in Python ext & Jupyter extension as well). |
We don't dispose controllers retrospectively (once it's been created). |
@DonJayamanne my vote is that it's also not a pressing issue. I'd also rather not check paths of interpreters (not ownership that we would want) from the python extension. I know that we don't remove controllers, but it is seen the first reload after deleting, probably the cache as we both mentioned. |
Issue Type: Bug
Old conda environments that have been deleted using
conda env remove --name <env_name>
are still showing up in the drop down menu of jupyter kernels.
They mention the old environment name as well as the location in the
anaconda/env/<env_name>
folder despite the fact that the folder no longer exists.When selected it throws out an error.
Extension version: 2020.12.414227025
VS Code version: Code 1.55.1 (08a217c4d27a02a5bcde898fd7981bda5b49391b, 2021-04-07T15:01:24.315Z)
OS version: Linux x64 5.8.0-48-generic snap
System Info
gpu_compositing: disabled_software
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
opengl: disabled_off
protected_video_decode: disabled_off
rasterization: disabled_software
skia_renderer: enabled_on
video_decode: disabled_software
vulkan: disabled_off
webgl: unavailable_software
webgl2: unavailable_software
A/B Experiments
The text was updated successfully, but these errors were encountered: