-
Notifications
You must be signed in to change notification settings - Fork 293
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
debug has stopped working for jupyter notebook #9118
Comments
@alexdauenhauer Thanks for the report. I'm not reproing it locally but it might be specific to your setup. Normally the log would have more info here, but for some reason that log seems really scanty. Is the jupyter.logging.level set to 'verbose'? |
@IanMatthewHuff thanks for the reply. I set
|
Was the step in stepping into something like a built in module? Or was it stepping into your code. Sorry about all the questions, but I can't repro this yet with my own setup. We do have a Jupyter specific Just my code debug setting that I'm wondering if is getting in the way. Could you turn off the Jupyter: Debug just my code setting and give that a try quick (you'll need to restart the kernel after changing that session). |
I think that I have narrowed it down a bit. It seems that it was only happening when I multiple remote kernels running on a single remote server. (i.e. when I start a separate notebook connecting to the same remote server, but start a separate kernel from within vscode, this is when the debugging starts to no longer work). |
Actually after running the same notebook locally, I think that the problem might be masked when running remotely. I think what might be happening is that it is not killing the debug PID after exiting the debugger. (i.e. start a debug cell, stop the debugging at some point, start it again, get the message "Invalid message: Session is already started"). I can only successfully enter debugging once I see this if I manually kill all python PIDs. I honestly have no idea if this is the same issue or a different issue than what I started this thread with |
@alexdauenhauer So just recently we've had some upstream issues from debugpy and ipython. Can you try this situation with making sure those are both up to date? |
pip install debugpy==1.6.0 Don't know why debugpy above 1.6.0 doesn't work in jupyter notebook but lower version no problem. |
Sorry, many changes since this issue |
Environment data
Expected behaviour
when I use
step into
orstep over
it would do this actionActual behaviour
nothing happens, code execution freezes, the only way to move forward is to restart the kernel
Steps to reproduce:
[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]
Logs
Output for
Jupyter
in theOutput
panel (View
→Output
, change the drop-down the upper-right of theOutput
panel toJupyter
)The text was updated successfully, but these errors were encountered: