-
Notifications
You must be signed in to change notification settings - Fork 294
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
No debugger available after restarting kernel #10741
Comments
I have the excact same problem. Also using vscode 1.69 and Jupyter extension v2022.6.1001902341 with python 3.9.12 in anaconda 4.13.0. |
It seems it always fails when I try to restart the debugging (which I should not do apparently):
Do you observe this too @alandema? |
Yes, @thisfro. It seems to be exactly this. |
Thanks for the bug report, we must not be handling the state change correctly. I can't get the specific behavior in the description, but if I disconnect an active debug session, and then restart the kernel, I see some unexpected behavior that's most likely related. (prompt to install IPykernel) |
Applies To
What happened?
-> Debug a cell
-> Stop debugger with disconnect (didn't find any other way to stop debugger)
The cell dropdown menu with debug option disappears. Need to run the cell to get que dropdown menu back.
-> If restar kernel
These toasts appears. Sometimes it does not affect anything, but sometimes you need to close and reopen VSCode to be able to run debugger again.
VS Code Version
1.69
Jupyter Extension Version
v2022.7.1001902022
Jupyter logs
No response
Coding Language and Runtime Version
Python 3.8.6
Language Extension Version (if applicable)
No response
Anaconda Version (if applicable)
No response
Running Jupyter locally or remotely?
Local
The text was updated successfully, but these errors were encountered: