-
Notifications
You must be signed in to change notification settings - Fork 960
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
Jupyter Notebooks in VSCode become unresponsive because the kernel gets disposed erroneously #1463
Comments
+1 to this problem, also documented on a vsCode repo issue here microsoft/vscode#214848 (comment), where @BabakAmini also narrowed the issue down to this extension I am also getting this issue on MacOS Ventura when connecting to a linux server over SSH. |
In my case, it was fixed after a couple of days of disabling and then re-enabling the extension. I had assumed that the recent update was the culprit, but now that it is failing, I have to disable it once more. |
I am having the same issue, can't use Continue with Jupyter in VSCode... |
Same issue here.... [info] Disposing request as the cell (-1) was deleted |
Hi, Same issue here when using from Ubuntu server via SSH. Here are my VScode logs :
|
Before submitting your bug report
Relevant environment info
Description
When using Continue with VSCode and connecting to a Jupyter Notebook in WSL, after about 3 minutes, the notebook becomes unresponsive and sends an error notification
NO notebook document for 'file:///path/to/notebook.ipynb'
The Jupyter output shows:
even though the notebook was not closed, and cells were not modified.
This issue was brought up in the vscode-jupyter github issues, but was closed once it was determined to be an issue with Continue.
To reproduce
Dispose Kernel
issueLog output
The text was updated successfully, but these errors were encountered: