Repository navigation
Cannot break in non-user code in 2025.0.1 #615
Description
After an update, the new no-config debug feature attaches to a listening debugpy server automatically, but it's no longer possible to set breakpoints in non-user code.
The option justMyCode seemed to be reset during the update, but disabling it in all possible locations in the settings didn't help. Only a rollback to 2024.14.0 made it possible again to break in non-user code.
In the documentation, I cannot find an explanation how to turn off the new no-config debug feature or choose the specific debug configuration I want to use. Please provide such an option to make this more controllable, thank you!
Activity
eleanorjboyd commentedon Feb 18, 2025
Hi! So the no-config debug does not connect to any settings set elsewhere you will need to provide them as arguments. Are you using the no-config debug or is this happening when you try and run a debug session with a config? If so can you explain more on how you are triggering debug and what your launch configurations are?
lukasgd commentedon Feb 19, 2025
Hi, thanks for the quick reply! Issue #617 seems to describe the same problem - as Rich Chiodo (@rchiodo) mentioned there, VScode is just automatically attaching, ignoring the configurations in
launch.jsonor other settings. While saving a click is nice, the no-config debug feature in its current form breaks quite a few user workflows, so my request was for an option to disable it.eleanorjboyd commentedon Feb 19, 2025
ok great thank you for looking at that other issue and totally makes sense. Closing this for now to centralize the conversation in the #617 issue and I will look into a solution now since this is definitely a bug that the feature interferes with this workflow. Thanks!