List of kernels shows deleted non-existent conda environments

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

Item	Value
CPUs	Intel® Core™ i7-8565U CPU @ 1.80GHz (8 x 3503)
GPU Status	2d_canvas: unavailable_software 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
Load (avg)	2, 2, 2
Memory (System)	15.49GB (0.21GB free)
Process Argv	–force-user-env --no-sandbox --unity-launch --no-sandbox --crash-reporter-id e0b4888e-7039-4296-a9e5-65e00d3fce86
Screen Reader	no
VM	0%
DESKTOP_SESSION	ubuntu
XDG_CURRENT_DESKTOP	Unity
XDG_SESSION_DESKTOP	ubuntu
XDG_SESSION_TYPE	x11

A/B Experiments

vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstry914:30276682
pythonvsdeb440:30248342
pythonvsded773:30248341
vstes627:30244334
pythonvspyt875:30259475
pythontb:30283811
openwsldoc:30282072
vspre833cf:30267465
pythonptprofiler:30281270
vshan820:30276952
pythondataviewer:30285071
vscus158:30286553

[DonJayamanne]

Conda env has been deleted. But it’s seen in the controller picker (deleteEnv2):

We don’t dispose controllers retrospectively (once it’s been created). And I think python returns the cached list the first time around. I’m not keen on checking the time paths as that will show the whole thing down even more. If anything I’d leave this around for more upvotes

[IanMatthewHuff]

@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.