Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Breakpoint in external py deactivates when debugging a Jupyter cell #16014

Open
2 tasks done
lenyabloko opened this issue Sep 8, 2024 · 0 comments
Open
2 tasks done
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug

Comments

@lenyabloko
Copy link

lenyabloko commented Sep 8, 2024

Applies To

  • Notebooks (.ipynb files)
  • 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

Screenshot 2024-09-07 214356

VS Code Version

1.93.0

Jupyter Extension Version

v2024.7.0

Jupyter logs

21:44:58.182 [debug] [Debug] to kernel: {"command":"continue","arguments":{"threadId":1},"type":"request","seq":45}
21:44:58.182 [debug] [Debug] to kernel, mapped: {"command":"continue","arguments":{"threadId":1},"type":"request","seq":45}
21:44:58.352 [debug] [Debug] response: {"seq":46,"type":"response","request_seq":45,"success":true,"command":"continue","body":{"allThreadsContinued":true}}
21:44:58.380 [debug] [Debug] event: {"header":{"msg_id":"9bdb5892-c157b44627c33ad0b9efe3b5_936_525","msg_type":"debug_event","username":"username","session":"9bdb5892-c157b44627c33ad0b9efe3b5","date":"2024-09-08T01:44:58.367890Z","version":"5.3"},"msg_id":"9bdb5892-c157b44627c33ad0b9efe3b5_936_525","msg_type":"debug_event","parent_header":{"date":"2024-09-08T01:44:58.183000Z","msg_id":"e90f92ea-afc5-401e-add3-c6b905b23102","msg_type":"debug_request","session":"a72bd563-25d6-48da-bd0e-1fc247de24f9","username":"","version":"5.2"},"metadata":{},"content":{"seq":47,"type":"event","event":"continued","body":{"threadId":1,"allThreadsContinued":true}},"buffers":[],"channel":"iopub"

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

@lenyabloko lenyabloko added the bug Issue identified by VS Code Team member as probable bug label Sep 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

2 participants