Activation issue: activation incorrectly using cmd not bat

[MatejVitek]

Uploading Python.log…
Type: Bug

Behaviour

Expected vs. Actual

Expected: I can code without interruptions.
Actual: Command prompt windows keep popping up, stealing focus from VSCode and making it difficult to write code.

Steps to reproduce:

I'm not certain how to reproduce the problem in general, but I've narrowed it down to the use of Pytest. After a clean reinstall, the issue wasn't present until I enabled Pytest in VSCode's Testing tab.

Studying the Python log in the Output tab, I noticed that whenever the window pops up, the following appears in the log:

2024-03-07 14:39:05.892 [info] Discover tests for workspace name: EyeZ - uri: c:\Users\matej\Documents\Programs\Python\EyeZ\eyez\data\sets\split.py
2024-03-07 14:39:05.898 [info] > conda run -n torch --no-capture-output python ~\.vscode\extensions\ms-python.python-2024.2.1\pythonFiles\get_output_via_markers.py ~\.vscode\extensions\ms-python.python-2024.2.1\pythonFiles\testing_tools\run_adapter.py discover pytest -- --rootdir ~\Documents\Programs\Python\EyeZ -s --cache-clear tests
2024-03-07 14:39:05.898 [info] cwd: ~\Documents\Programs\Python\EyeZ

Trying to exectue the above conda run command manually gives me an error, since ~ is not a thing in powershell or command prompt.

This issue only started appearing in the last month or two, prior to that I could use Pytest on the same machine with no issues.

Diagnostic data

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

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

Python log attached, since it was too long to copy here.

User Settings

Multiroot scenario, following user settings may not apply:

languageServer: "Pylance"

testing
• pytestArgs: "<placeholder>"
• pytestEnabled: true

Extension version: 2024.2.1
VS Code version: Code 1.87.0 (019f4d1419fbc8219a181fab7892ebccf7ee29a2, 2024-02-27T23:41:44.469Z)
OS version: Windows_NT x64 10.0.19045
Modes:

System Info

Item	Value
CPUs	AMD Ryzen 7 2700X Eight-Core Processor (16 x 3700)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: enabled_on 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_graphite: disabled_off video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled
Load (avg)	undefined
Memory (System)	31.95GB (19.90GB free)
Process Argv
Screen Reader	no
VM	0%

[mlamarre]

I have the same issue with test discovery triggering a pop-up. Corresponds to the log below in the Output->Python.

2024-03-11 14:49:00.483 [info] Discover tests for workspace name: [***removed path***]
2024-03-11 14:49:00.483 [info] Running discovery for unittest using the new test adapter.
2024-03-11 14:49:00.488 [info] Discovering unittest tests for workspace [***removed path*** with arguments: [***removed path***\.vscode\extensions\ms-python.python-2024.2.1\pythonFiles\unittestadapter\discovery.py,--udiscovery,-v,-s,./tests,-p,test*.py

2024-03-11 14:49:00.489 [info] > D:\miniforge\Scripts\conda.exe run -n [removed name] --no-capture-output python ~\.vscode\extensions\ms-python.python-2024.2.1\pythonFiles\get_output_via_markers.py ~\.vscode\extensions\ms-python.python-2024.2.1\pythonFiles\unittestadapter\discovery.py --udiscovery -v -s ./tests -p test*.py
2024-03-11 14:49:00.489 [info] cwd: .
2024-03-11 14:49:01.644 [info] >>>PYTHON-EXEC-OUTPUT

2024-03-11 14:49:05.390 [info] Test server connected to a client.
2024-03-11 14:49:05.395 [info] Test server connected to a client.
2024-03-11 14:49:05.395 [info] <<<PYTHON-EXEC-OUTPUT

2024-03-11 14:49:05.396 [info] ResultResolver EOT received for discovery.

[eleanorjboyd]

Hi! Could you provide a screenshot of this popup you are referencing? I am not sure exactly what you are talking about. Thanks!

[MatejVitek]

Kinda hard to get a screenshot since the popup is so short. Here's a video showing the issue.

Untitled.video.-.Made.with.Clipchamp.mp4

In the video I change the code and save the file (CTRL + S) to trigger a test rediscovery.

The popup doesn't appear in other workspaces, only Python workspaces with testing set up.

[eleanorjboyd]

thanks for the video, that is very helpful! I have never seen this issue before- let me talk with some colleagues and circle back.

[eleanorjboyd]

one quick question: do you have any workspace or user settings having to do with saving like "python.workspaceSymbols.rebuildOnFileSave" or "python.testing.autoTestDiscoverOnSaveEnabled" ? Curious if turning either of these to false changes the behavior

[MatejVitek]

I didn't have either of those two in my settings files (attaching here both my user settings.json
and the settings.json in the .vscode folder in the workspace). My .code-workspace files only contain folder paths and launch configurations, no extra settings.

I tried adding the two settings and changing their values, but it didn't seem to have any effect. The test discovery still runs and triggers a popup, regardless of the two settings.

[eleanorjboyd]

@karthiknadig any ideas here? I am not seeing any settings that I think could trigger this

[karthiknadig]

Do we use shell execute when running tests? If that is yes, then command prompt initialization script that sets up conda or any other thing might be a cause of this. Each time we run something using shell execute, it will attempt to run initialization. I would check the init script that conda init adds first.