microsoft / microsoft/vscode-python-debugger
Python Debugger error when starting test in debug "Invalid message: Found duplicate in "env": Path"
Open
@eleanorjboyd is already working on this.
Since Oct 3, 2025.
- Dominant language
- TypeScript
- Stars
- 180
- Forks
- 126
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 3
Description
When attempting to launch a single test in debug mode using the Python Debugger extension, VS Code immediately fails and shows an error dialog: Invalid message: Found duplicate in "env": PATH.
Extension version: 2025.10.0
VS Code version: Code 1.103.2 (6f17636121051a53c88d3e605c491d22af2ba755, 2025-08-20T16:45:34.255Z)
OS version: Windows_NT x64 10.0.26100
Modes:
- Python version (& distribution if applicable, e.g. Anaconda): 3.13.7
- Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): VirtualEnvironment
System Info
| Item | Value |
|---|---|
| CPUs | 13th Gen Intel(R) Core(TM) i7-1360P (16 x 2611) |
| GPU Status | 2d_canvas: enabled 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 trees_in_viz: disabled_off video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off |
| Load (avg) | undefined |
| Memory (System) | 63.71GB (53.10GB free) |
| Process Argv | linkedin-jobs-url/ --crash-reporter-id 89e519a1-7b57-4e47-a9dd-158e0d0fc56b |
| Screen Reader | no |
| VM | 0% |
A/B Experiments
vsliv368:30146709
binariesv615:30325510
nativeloc1:31344060
dwcopilot:31170013
dwoutputs:31242946
copilot_t_ci:31333650
e5gg6876:31282496
996jf627:31283433
pythonrdcb7:31342333
usemplatestapi:31297334
aj953862:31281341
nesew2to5:31336538
agentclaude:31350858
nes-set-on:31351930
6abeh943:31336334
0927b901:31350571
ovs_c:31383294
45650338:31358607
0cj2b977:31352657
gaj49834:31362110
asdad:31365766
cloudbuttont:31379625
retryenabled:31370050
3efgi100_wstrepl:31382709
trigger-command-fix:31379601
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.