Environment Manager can't see New VENV despite being created by the extension.

[futuremotiondev]

Type: Bug

Behaviour

Expected vs. Actual

I have a small VSCode workspace that I created solely for Python development. I have two virtual environments (venv). One of them (Font Tools) was created through the plugin itself.

My problem is that the environment manager can only see one of the venv environments.

Expected: Both environments to be listed.
Actual: Only one environment is listed.

Steps to reproduce:

I'm not exactly sure how to reproduce, other than re-creating the structure of my workspace in VSCode and then creating the virtual environments.

Diagnostic data

• Python version (& distribution if applicable, e.g. Anaconda):
• Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Unknown
• Value of the python.languageServer setting: Default

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

XXX

User Settings

languageServer: "Pylance"

Extension version: 1.0.4
VS Code version: Code 1.70.1 (6d9b74a70ca9c7733b29f0456fd8195364076dda, 2022-08-10T06:08:33.642Z)
OS version: Windows_NT x64 10.0.19044
Modes:

System Info

Item	Value
CPUs	Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz (16 x 3600)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_renderer: enabled_on video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled
Load (avg)	undefined
Memory (System)	63.92GB (52.62GB free)
Process Argv	D:\Dev\Python\python.code-workspace --crash-reporter-id 980edeb0-3f45-42f4-8995-c0d13015b889
Screen Reader	no
VM	0%

[futuremotiondev]

Here are screenshots to further clarify what is happening. This is my workspace:

And this is the environment manager (only showing one environment):

And yes, I've tried clicking the "Refresh Envrionments" button.

I think it would be helpful if someone could elaborate on how the plugin detects VENVs. Maybe that would help me resolve this issue.

[web4zn]

I can't see all my venv, do you know how to fix it ?

[Throdne]

Possible related, but the "Refresh Environments" button doesn't seem to work. I install virtualenv in the global packages and hitting the refresh button doesn't load the new package.

The only way I'm able to refresh the view is to close Visual Studio Code, then reopen. This will now show the new packages in the global packages list.