Unexpected configuration merging behavior for justMyCode debugging option
維護者通常 5 天內回覆
@rchiodo 已經在處理了。
開始於 2025年8月14日。
評估
這個 Issue 還沒有評估資料。
描述
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.
- 主要語言
- TypeScript
- 星號
- 181
- 分支
- 126
- 平均合併
- 14 天 4 小時
- 30 天內合併 PR
- 2
環境準備
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
microsoft/vscode-python-debugger 的其他 Issue
-
triage-needed
難度 2/5 1-3 小時 新手友好度 78/100
microsoft/vscode-python-debugger#1110 ·
維護者通常 5 天內回覆
-
triage-needed
難度 1/5 1-3 小時 新手友好度 88/100
microsoft/vscode-python-debugger#1024 · 1 則留言 ·
維護者通常 5 天內回覆
-
Update dependencies with actionable security alerts可能已有人在做 @copilot-swe-agent 於 15 天前認領。 未關閉triage-needed
microsoft/vscode-python-debugger#1111 · 1 個 reaction · 已指派 1 人 ·
維護者通常 5 天內回覆
-
Update vulnerable npm dependencies可能重新可做 關聯的 PR 已關閉且未合併。 未關閉triage-needed
microsoft/vscode-python-debugger#1104 · 1 個 reaction · 已指派 1 人 ·
維護者通常 5 天內回覆
-
triage-needed
難度 4/5 3-5 天 新手友好度 45/100
microsoft/vscode-python-debugger#1052 · 2 則留言 ·
維護者通常 5 天內回覆
查看 microsoft/vscode-python-debugger 的全部 Issue
相似的 Issue
-
area/core status/need-triage
難度 2/5 1-3 小時 新手友好度 88/100
google-gemini/gemini-cli#29602 ·
維護者通常 1 天內回覆
-
area: backend enhancement priority: low
難度 2/5 1-3 小時 新手友好度 88/100
snapotter-hq/SnapOtter#1879 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 86/100
Tencent/BrowserSkill#390 ·
維護者通常 1 天內回覆
-
good first issue status: needs triaging type: bug version: 2.0
難度 2/5 1-3 小時 新手友好度 85/100
medusajs/medusa#17094 · 2 則留言 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 86/100
維護者通常 1 天內回覆