Unexpected configuration merging behavior for justMyCode debugging option
@rchiodo y travaille déjà.
Depuis le 14/8/2025.
Évaluation
Cette issue n'a pas encore été évaluée.
Description
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.
- Langage dominant
- TypeScript
- Étoiles
- 181
- Forks
- 126
- Merge moyen
- 8 h 49 min
- PR mergées (30 j)
- 1
Guide de contribution
Ouvrir le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de microsoft/vscode-python-debugger
-
triage-needed
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
microsoft/vscode-python-debugger#1110 ·
-
triage-needed
Difficulté 1/5 1-3 heures Accessibilité débutants 88/100
microsoft/vscode-python-debugger#1024 · 1 commentaire ·
-
triage-needed
microsoft/vscode-python-debugger#1111 · 1 réaction · 1 personne assignée ·
-
triage-needed
microsoft/vscode-python-debugger#1104 · 1 réaction · 1 personne assignée ·
-
triage-needed
Difficulté 4/5 3-5 jours Accessibilité débutants 58/100
microsoft/vscode-python-debugger#1095 · 1 commentaire · 1 réaction ·
Toutes les issues de microsoft/vscode-python-debugger
Issues similaires
-
VerificationGate: ATTRIBUTION quote guard never matches a normal quotation (\b around the quote) Ouverte
Difficulté 2/5 1-3 heures Accessibilité débutants 75/100
danielmiessler/LifeOS#2234 ·
-
T: Bug
Difficulté 2/5 1-3 heures Accessibilité débutants 75/100
-
Difficulté 2/5 1-3 heures Accessibilité débutants 65/100
-
Difficulté 1/5 Moins d'une heure Accessibilité débutants 85/100
-
Mend: dependency security vulnerability untriaged
Difficulté 2/5 1-3 heures Accessibilité débutants 70/100