You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running an interactive debug session with debugpy, the debugger stops at subprocess breakpoints, but the current line is highlighted green instead of yellow.
Note, that there's no arrow on the breakpoint line (117), that the subprocess stack frames weren't loaded on the call stack panel, and that the variables panel is empty. If I then click on "Show 6 More Stack Frames" and select the first stack frame, the arrow appears on the current line and the variables panel is properly filled.
However, if I step over to the next line, the same problem shown on the first picture happens again.
I believe this behavior could be caused by the recent changes on the Debug Stack Focus API introduced on the latest VS Code release (version 1.90).
When running an interactive debug session with debugpy, the debugger stops at subprocess breakpoints, but the current line is highlighted green instead of yellow.
Note, that there's no arrow on the breakpoint line (117), that the subprocess stack frames weren't loaded on the call stack panel, and that the variables panel is empty. If I then click on "Show 6 More Stack Frames" and select the first stack frame, the arrow appears on the current line and the variables panel is properly filled.
However, if I step over to the next line, the same problem shown on the first picture happens again.
I believe this behavior could be caused by the recent changes on the Debug Stack Focus API introduced on the latest VS Code release (version 1.90).
This is what my launch.json looks like:
Is this a bug, or am I missing some new configuration?
The text was updated successfully, but these errors were encountered: