Unexpected configuration merging behavior for justMyCode debugging option
@rchiodo arbeitet bereits daran.
Seit 14.8.2025.
Bewertung
Dieses Issue wurde noch nicht bewertet.
Beschreibung
In #139, many people have reported being unable to use justMyCode as expected. While there is a workaround in the linked comment, I believe it ultimately stems from the global debugpy.debugJustMyCode overwriting the launch configuration option, which I think is unexpected.
I had always been relying on the launch-configuration-level setting of
justMyCodebeing set tofalseto be sufficient. Is the extension perhaps not merging the different levels of configs as expected and leading to the defaultdebugpy.debugJustMyCodeto trump the launch-configuration-leveljustMyCodewhen specified in.code-workspacefiles?
Originally posted by @tboddyspargo in #139
I wanted to repost this here in an effort to specifically focus on the question of configuration merging behavior.
I expect the repro to be something like:
- Specify a python special
purposefile or test debug configuration (with"justMyCode": false) in the launch configuration of a.code-workspacefile. - Open that workspace and debug a python script using that launch configuration.
- Try to step into library code using the debugger
- Repeat this step, since the repro steps in https://github.com/microsoft/vscode-python-debugger/issues/139#issuecomment-1821800403 sometimes indicate that the "first time" succeeds and subsequent ones do not.
- Based on my previous experience and the other reports in #139, I expect this to not go into library code during the "subsequent" debug sessions (frame skipped message?)
However I also think that, even without repro-ing, it may be reasonable to re-examine the config merging behavior of debugpy.debugJustMyCode with workspace-level launch configuration settings to definitively debug the root cause hypothesis here or confirm it.
- Vorherrschende Sprache
- TypeScript
- Sterne
- 181
- Forks
- 126
- Ø Merge
- 2 T. 3 Std.
- Gemergte PRs (30 T.)
- 3
Beitragsleitfaden
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus microsoft/vscode-python-debugger
-
triage-needed
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
microsoft/vscode-python-debugger#1110 ·
-
triage-needed
Schwierigkeit 1/5 1-3 Stunden Anfängerfreundlichkeit 88/100
microsoft/vscode-python-debugger#1024 · 1 Kommentar ·
-
triage-needed
microsoft/vscode-python-debugger#1111 · 1 Reaktion · 1 zugewiesene Person ·
-
triage-needed
microsoft/vscode-python-debugger#1106 · 1 Reaktion · 2 zugewiesene Personen ·
-
triage-needed
microsoft/vscode-python-debugger#1104 · 1 Reaktion · 1 zugewiesene Person ·
Alle Issues in microsoft/vscode-python-debugger
Ähnliche Issues
-
Type/Bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
OpenNSW/nsw-srilanka#497 ·
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
0xMiden/bridge-portal#132 ·
-
react-doctor severity:warning tech-debt
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 88/100
digidem/comapeo-cloud-app#403 ·
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100