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
Interactive Window and/or Cell Scripts (.py files with #%% markers)
What happened?
Debugging a notebook running on a remote Jupyter server accessed by Windows 11 VScode via WSL2 localhost kernel.
Expected debugger to stop at the breakpoint set in external py file called from a Jupyter cell.
Before pressing a 'Debug Cell', the external py files is listed under BREAKPOINTS in Debug window and shows the red dot before its name.
As soon as 'Debug Cell' pressed, the red dot disappears and shows a tooltip message when mouse over the py file name: Breakpoint is set in file that does not exists
Debug console shows error attaching to process Id
Applies To
What happened?
Debugging a notebook running on a remote Jupyter server accessed by Windows 11 VScode via WSL2 localhost kernel.
Expected debugger to stop at the breakpoint set in external py file called from a Jupyter cell.
Before pressing a 'Debug Cell', the external py files is listed under BREAKPOINTS in Debug window and shows the red dot before its name.
As soon as 'Debug Cell' pressed, the red dot disappears and shows a tooltip message when mouse over the py file name:
Breakpoint is set in file that does not exists
Debug console shows
error attaching to process Id
VS Code Version
1.93.0
Jupyter Extension Version
v2024.7.0
Jupyter logs
Coding Language and Runtime Version
Python and/or Anaconda version: Python 3.11.2
Language Extension Version (if applicable)
Python Extension version: v2024.12.2
Anaconda Version (if applicable)
No response
Running Jupyter locally or remotely?
Remote
The text was updated successfully, but these errors were encountered: