Environment in workspace is not detected on open

[jakebailey]

Issue Type: Bug

Behaviour

Expected

The environment is selected or at least available.

Actual

The environment does not appear in the list.

Steps to reproduce:

python -m venv .venv
code .

Diagnostic data

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

"Python" channel in the OUTPUT panel

User belongs to experiment group 'pythonaacf'
User belongs to experiment group 'pythonJediLSP'
User belongs to experiment group 'pythonDiscoveryModuleWithoutWatcher'
User belongs to experiment group 'pythonTensorboardExperiment'
User belongs to experiment group 'PythonPyTorchProfiler'
User belongs to experiment group 'CollectLSRequestTiming - control'
User belongs to experiment group 'CollectNodeLSRequestTiming - experiment'
User belongs to experiment group 'DeprecatePythonPath - experiment'
> python c:\Users\jabaile\.vscode\extensions\ms-python.python-2021.4.765268190\pythonFiles\pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> python c:\Users\jabaile\.vscode\extensions\ms-python.python-2021.4.765268190\pythonFiles\pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
Error 2021-05-06 15:25:30: Failed to check if file needs to be fixed [EntryNotFound (FileSystemError): Unable to read file 'e:\work\test_projects\attrstest\.vscode\settings.json' (Error: Unable to resolve non-existing file 'e:\work\test_projects\attrstest\.vscode\settings.json')
	at _handleError (c:\Users\jabaile\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:87:156171)
	at runMicrotasks (<anonymous>)
	at processTicksAndRejections (internal/process/task_queues.js:93:5)
	at async y.readText (c:\Users\jabaile\.vscode\extensions\ms-python.python-2021.4.765268190\out\client\extension.js:9:339523)
	at async p.doesFileNeedToBeFixed (c:\Users\jabaile\.vscode\extensions\ms-python.python-2021.4.765268190\out\client\extension.js:59:577126)
	at async c:\Users\jabaile\.vscode\extensions\ms-python.python-2021.4.765268190\out\client\extension.js:59:576253
	at async Promise.all (index 1)
	at async p.getFilesToBeFixed (c:\Users\jabaile\.vscode\extensions\ms-python.python-2021.4.765268190\out\client\extension.js:59:576199)
	at async p.updateTestSettings (c:\Users\jabaile\.vscode\extensions\ms-python.python-2021.4.765268190\out\client\extension.js:59:575826)] {
  code: 'FileNotFound'
}
Python interpreter path: ~\scoop\apps\python38\3.8.10\python.exe
Starting Pylance language server.

Extension version: 2021.4.765268190
VS Code version: Code 1.56.0 (cfa2e218100323074ac1948c885448fdf4de2a7f, 2021-05-04T22:09:06.405Z)
OS version: Windows_NT x64 10.0.19043

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz (8 x 3600)
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)	63.79GB (46.81GB free)
Process Argv	. --crash-reporter-id 040749e8-68ab-4dfe-8282-d1310ad45b21
Screen Reader	no
VM	0%

A/B Experiments

vsins829:30139715
vsliv368:30146709
vsreu685:30147344
vspor879:30202332
vspor708:30202333
vspor363:30204092
vspre833cf:30267465
vshan820:30294714
vscoreces:30290705
vscus158:30286553

[mripani]

Hello!

I think I have this same problem over here.

I create the virtualenv from the Visual Studio Code terminal. The comands I ran were:
python3 -m venv kagglemay_env

Then tried to select the Python interpreter recently created and it doesn't appear.

System Info

MAC OS Catalina 10.15.7
VSC Code 1.56.0

[karthiknadig]

@mripani Can you try the 'refresh' button at the top and see if that helps?

[mripani]

@karthiknadig I already solved it. It was a matter of restarting Visual Studio Code after creating the virtualenv and then it magically appears.

[karthiknadig]

@mripani I see. We have watchers that should detect when you create and environment in your workspace. Usually you will see a notification that says we have detected an new environment. I guess that part did not work? When you restart we do a full search so it will find the new environment. Same with refresh, we do a full search, that should also find the new environment.

[mripani]

I understand. Maybe the watchers are not working properly. When I had the problem I tried with the refresh button and it didn't work out. I will try again the next time I create a virtualenv.

[jakebailey]

FWIW I hit this again in a new folder, and the refresh button did nothing.

[karthiknadig]

This should now be fixed.