conda environment not visible

[CLWilliam]

Issue Type: Bug

• install conda: conda base environment present
• create new environment in the shell
• Reload window
• When selecting the interpretter, the the base environment ('base': conda) always shows up. The newly created environments are visible for a fraction of a second but than disappear from the list, indicating me that vscode does find them but does not show them for some reason. Cannot find a relevant setting to solve this, which makes me think it's a bug.

Thanks in advance!

VS Code version: Code 1.63.2 (899d46d82c4c95423fb7e10e68eba52050e30ba3, 2021-12-15T09:40:02.816Z)
OS version: Windows_NT x64 10.0.22000
Restricted Mode: No

System Info

Item	Value
CPUs	AMD Ryzen 5 3600 6-Core Processor (12 x 3950)
GPU Status	2d_canvas: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on rasterization: enabled skia_renderer: enabled_on video_decode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled
Load (avg)	undefined
Memory (System)	31.89GB (26.63GB free)
Process Argv	--crash-reporter-id 4852a6f8-eb51-4f59-a441-70dab126d586
Screen Reader	no
VM	0%

Extensions (6)

Extension	Author (truncated)	Version
python	ms-	2021.12.1559732655
vscode-pylance	ms-	2021.12.2
jupyter	ms-	2021.11.1001550889
jupyter-keymap	ms-	1.0.0
jupyter-renderers	ms-	1.0.4
powershell	ms-	2021.12.0

A/B Experiments

vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30384386
pythondataviewer:30285071
vscod805:30301674
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30410667
vscop804:30404766
vscop940:30404999
vsrem710:30416614
vscexrecpromp3t1:30407762

[karthiknadig]

@CLWilliam Can you provide logs from Output > Python? this can happen for two reasons, if you are using python 3.10 with conda then there is a bug in conda that breaks (see here for conda bug and workaround conda/conda#11072) . If it is not python 3.10, then it could be that we are not able to run the interpreter for some reason and the logs should tell.

[CLWilliam]

It indeed seems to be related to conda and python 3.10. python 3.9 does not have this issue. Thanks alot, @karthiknadig !