Invalid message: Found duplicate in "env": PATH when using virtual environment in Python 3.11

[Youssefbenhammouda]

Type: Bug

I get this error "Invalid message: Found duplicate in "env": PATH." when I use a Virtual environment to debug python code, but when I switch to the global python interpreter it works fine.

Extension version: 2023.5.10681722
VS Code version: Code - Insiders 1.77.0-insider (b60db78000bfa99d1b290194ed4651c4ceef02cc, 2023-03-10T05:24:23.805Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: Yes

A/B Experiments

vsliv695:30137379
vsins829:30139715
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256198
vstes627:30244334
vslsvsres303:30308271
pythonvspyl392:30422396
pythontb:30258533
vsc_aacf:30263846
pythonptprofiler:30281269
vshan820:30294714
pythondataviewer:30285072
vscod805:30301674
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30404738
cppdebug:30492333
vsclangdf:30492506
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30618038
pylantcb52:30590116
pyindex848:30611229
nodejswelcome1:30587009
pyind779:30611226
pythonsymbol12:30651887
6233i204:30659907
pythonb192cf:30661257
funwalk2cf:30682975
pythonms35:30671666
03d35959:30680466
7ij38806:30677315

[karrtikr]

Can you use Python: Report Issue command instead, it auto-fills many of the details we need? Other than that:

• Please provide the launch.json config you're trying to debug with.
• Please provide the logs after debugging:

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

XXX

[Youssefbenhammouda]

    "launch": {
        "configurations": [{
            "name": "Python: Current File",
            "type": "python",
            "request": "launch",
            "program": "${file}",
            "cwd": "${workspaceFolder}",
            "console": "internalConsole",
            "justMyCode": true
        }]

Here's the output after debugging:
DAP Server launched with command: c:\Users{user}\Projects\python\simpleApp\venv\Scripts\python.exe c:\Users{user}.vscode-insiders\extensions\ms-python.python-2023.5.10681722\pythonFiles\lib\python\debugpy\adapter

[karrtikr]

Please provide the debug logs, set python.logging.level to debug in User settings, reload window, then perform the steps to reproduce before providing the logs.

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

XXX

[karrtikr]

Perhaps .env file or some other file is sending the PATH variable.

[bersbersbers]

Same issue here with v1.77.0 and v2023.6.0.

[bersbersbers]

My launch config:

{
            "name": "project",
            "type": "python",
            "purpose": [
                "debug-in-terminal",
                // https://github.com/microsoft/vscode-python/issues/19030
                // "debug-test",
            ],
            "request": "launch",
            "program": "project/project.py",
            "args": [
            ],
            // Comment out to inspect additional output
            "console": "internalConsole",
            "justMyCode": false,
        },

Removing "console": "internalConsole" fixes the symptoms of the issue.

[karrtikr]

Do you have a .env file somewhere specifying additional env vars? Please mention the contents if so.

[pppmlt]

I have the same issue since the latest update.. Without "console": "internalConsole" the code runs fine (but not in internal console).

launch.json

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
                "name": "Python: Module",
                "type": "python",
                "request": "launch",
                "program": "${workspaceFolder}/${relativeFileDirname}/${fileBasename}",
                "env": {"PYTHONPATH": "${workspaceFolder}", "CONDA_PREFIX": "PATH\\TO\\CONDA\\ENV"},
                "console": "internalConsole",
                "internalConsoleOptions": "openOnSessionStart",
        }
    ]
}

vscode

Version: 1.77.0 (system setup)
Commit: 7f329fe6c66b0f86ae1574c2911b681ad5a45d63
Date: 2023-03-29T10:02:16.981Z
Electron: 19.1.11
Chromium: 102.0.5005.196
Node.js: 16.14.2
V8: 10.2.154.26-electron.0
OS: Windows_NT x64 10.0.19042
Sandboxed: Yes

[svenmk]

The same here. Everything worked nicely. Just updated this morning, now I'm getting the error when debugging tests. Without debugging, they run.

I'm not having any .env file in my project dir.

{
    "version": "0.2.0",
    "configurations": [  
        {
            "name": "Python: Current File",
            "type": "python",
            "request": "launch",
            "program": "${file}",
            "console": "integratedTerminal",
            "justMyCode": true
        },
        {
            "name": "Debug Unit Test",
            "type": "python",
            "request": "test",
            "justMyCode": true,
            "env": {
                "PYTEST_ADDOPTS": "--no-cov",
            }
        }
    ]
}

PS> code -v
1.77.0
7f329fe6c66b0f86ae1574c2911b681ad5a45d63
x64

[bersbersbers]

Do you have a .env file somewhere specifying additional env vars? Please mention the contents if so.

C:\>dir .env /a /s /b
C:\Users\bers\.vscode\extensions\donjayamanne.python-environment-manager-1.0.4\pythonFiles\.env
C:\Users\bers\.vscode\extensions\ms-python.python-2023.6.0\pythonFiles\.env

C:\>more C:\Users\bers\.vscode\extensions\donjayamanne.python-environment-manager-1.0.4\pythonFiles\.env
PYTHONPATH=./lib/python

C:\>more C:\Users\bers\.vscode\extensions\ms-python.python-2023.6.0\pythonFiles\.env
PYTHONPATH=./lib/python

[svenmk]

I just downgraded the Python plugin from version v2023.6.0 to v2023.4.1 -> solved the issue. Something is wrong in the current release.

Please keep in mind this can only be a workaround!

[yuriy-osnadchuk]

I downgraded the plugin, and the issue is gone. Thanks, svenmk

[jasonboh]

same issue here

[johnjmur0]

Same issue, downgrading also worked.

[rthompson-dcgis]

Having the same issue. I will try to downgrade.

[rthompson-dcgis]

Downgrading to 2023.4.1 solved the issue for me as well.

[rtsaad]

Having the same issue; Downgrading to 2023.4.1 solved the issue for me as well.

[MasterGeorges67]

Downgrading to 2023.4.1 solved the issue for me as well.

[JakubFranek]

I guess it is pretty established downgrading solves this issue now (and it has fixed the problem for me too), but the question is: is this a bug or a feature? Is there actually something wrong with the environments of the users experiencing this issue, this error message is correctly flagging it and the users should fix the problem on their side, or is it a "false positive"?

[websniff64]

Having the same issue, downgrading to 2023.4.1 fixed my issue.
It's just a workaround ...

[metamoof]

I can confirm that downgrading to 2023.4.1 also fixed the issue for me. Hopefully this issue will be resolved soon...

[Amourspirit]

Downgrading to 2023.4.1 solved the issue for me as well !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Me as well.

Also:

• Windows 10
• Using virtual environment for python 3.8
• Working on project OOO Development Tools

[haoy-zzz]

I have the same problem.
Thanks a lot.

[QuintusHegie]

I have the same issue with Visual Studio Code 1.77.1 on Windows_NT x64 10.0.19045 and dated 2023-04-04T23:21:11.

My setup worked in a previous version of VS Code and plugins, a week or 2 ago.

I work with a .venv subfolder, which I activate / is activated in the console when my VS Code projects opens.

For the Run and Debug configuration I use the reference to environment files. Same holds for Testing.

I found a way around it for Run and Debug by manually editing the VS code settings file, but not yet for the Testing.

See below settings file.

• I can run the 1st launch configuration fine, but not the 2nd (labelled release).
• When I change the python.envFile to match the release.env of the 2nd launch config, then I can launch the 2nd configuration, but the 1st configuration will (obviously) then also implicitly take release.env from the python.envFile.

The finding hints to me that previously either one or the other environment file is loaded. The specific launch configuration one overwrites the default one. But after the update probably both environment files get loaded, resulting in the reported error.

{
	"settings": {
		"python.envFile": "${workspaceFolder}/.env",
	},
	"launch": {
		"version": "0.2.0",
		"configurations": [
			{
				"name": "Python: main.py",
				"type": "python",
				"request": "launch",
				"program": "main.py",
				"console": "integratedTerminal"
			},
			{
				"name": "Python: main.py [release]",
				"type": "python",
				"request": "launch",
				"program": "main.py",
				"console": "integratedTerminal",
				"envFile": "${workspaceFolder}/release.env"
			}
		]
	}
}

Hope this helps debugging the issue.

[karrtikr]

Fix should be out in the pre-release version of the extension, use the following to try it out:

[javiermtl]

please, could you share the command to downgrade it to 2023.4.1?

[karrtikr]

@javiermtl Downgrading should be no longer needed, try pre-release mentioned in #20828.

[javiermtl]

@javiermtl Downgrading should be no longer needed, try pre-release mentioned in #20828.

Thanks, @karrtikr, it worked for me :)

[svenmk]

I can confirm that the problem is solved for me in the Pre-Release version. Thank you!

[TcDhlPro]

I can confirm that the problem is solved for me in the Pre-Release version. Thank you!

Me Too!

[AlexCaranha]

Thanks, it worked for me.

[ppmarkus]

Thanks @kartik. Works well now.

[karrtikr]

Thanks everyone for confirming, we'll release a stable version with the fix very soon.