Search results

Add a <code>debugpy.sh</code> for the no-config debugging

bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bug

good first issueGood for newcomersGood for newcomers

Status: Open.

#651 In microsoft/vscode-python-debugger;

·karthiknadig openedon Mar 5, 2025

Long string values probably should not be inlined

bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bug

Status: Open.

#404 In microsoft/vscode-python-debugger;

·karthiknadig openedon Jul 23, 2024

Cannot read properties of undefined (reading 'resolveEnvironment')

bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bug

needs spike

triage-neededNeeds assignment to the proper sub-teamNeeds assignment to the proper sub-team

Status: Open.

#333 In microsoft/vscode-python-debugger;

·hk0624 openedon May 2, 2024

I don't see the eye icon in the Python debugger variables view

bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bug

Status: Open.

#324 In microsoft/vscode-python-debugger;

·aeschli openedon Apr 23, 2024

Unable to debug tests: Invalid message: Found duplicate in "env": PATH

bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bug

good first issueGood for newcomersGood for newcomers

info-neededIssue requires more information from posterIssue requires more information from poster

needs PRReady to be worked onReady to be worked on

Status: Open.

#261 In microsoft/vscode-python-debugger;

·DudeNr33 openedon Mar 12, 2024

Check on debug launch configuration's <code>python</code> field prevents container debugging

bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bug

needs PRReady to be worked onReady to be worked on

Status: Open.

Bug

#531 In microsoft/vscode-python-debugger;

·bwateratmsft openedon Feb 6, 2024

· 

July 2025

Attaching python debugger fails in rarely

bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bug

needs spike

Status: Open.

#179 In microsoft/vscode-python-debugger;

·cedric-fauth openedon Dec 5, 2023

$PATH ordering is wrong when running with Python debugger.

bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bug

needs PRReady to be worked onReady to be worked on

Status: Open.

#258 In microsoft/vscode-python-debugger;

·tbenthompson openedon Apr 24, 2022

Read test debug configuration from settings not just launch.json

bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bug

triage-neededNeeds assignment to the proper sub-teamNeeds assignment to the proper sub-team

Status: Open.

Bug

#532 In microsoft/vscode-python-debugger;

·ElPincheTopo openedon Mar 25, 2022

· 

July 2025

Debug flow

bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bug

needs PRReady to be worked onReady to be worked on

Status: Open.

Bug

#527 In microsoft/vscode-python-debugger;

·bamurtaugh openedon Nov 30, 2021

Option "execute in file dir" ignored when use play button "debug python file in terminal"

bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bug

needs PRReady to be worked onReady to be worked on

Status: Open.

#257 In microsoft/vscode-python-debugger;

·Diogo-Rossi openedon Oct 8, 2021

[BUG] Debugging with purpose ignored in user/workspace settings.

bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bug

needs PRReady to be worked onReady to be worked on

Status: Open.

Bug

#525 In microsoft/vscode-python-debugger;

·byehack openedon Oct 6, 2021