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?
Every so often—often within 10 minutes—the interactive window seems to "disconnect" from the running Jupyter kernel. Any additional attempts to execute cells just queue up and do nothing (see screenshot). Hitting the restart button brings up the UI elements associated with restarting the kernel but that process continues indefinitely and never completes.
I'm pretty confident the issue is not with Jupyter since I can connect to initial kernel from the Jupyter Lab web interface and everything works normally. The kernel remains available from Jupyter Lab even after hitting restart in VSCode.
I did not used to have this issue with earlier versions of VSCode and the extension (though I don't know ATM exactly which version the problem first appears).
The disconnection occurs right around the time of the repeated "CodeLensFactory" lines at the end of the log. Nothing other actions show up in the log once in this "disconnected" state except for the kernel restart request.
(The VSCode version pasted below is 1.95.3, but I get the same behavior with 1.96.0 and 1.96.2. I was also using 2024.11.0 of the extension then and still had the problem.)
Applies To
What happened?
Every so often—often within 10 minutes—the interactive window seems to "disconnect" from the running Jupyter kernel. Any additional attempts to execute cells just queue up and do nothing (see screenshot). Hitting the restart button brings up the UI elements associated with restarting the kernel but that process continues indefinitely and never completes.
I'm pretty confident the issue is not with Jupyter since I can connect to initial kernel from the Jupyter Lab web interface and everything works normally. The kernel remains available from Jupyter Lab even after hitting restart in VSCode.
I did not used to have this issue with earlier versions of VSCode and the extension (though I don't know ATM exactly which version the problem first appears).
The disconnection occurs right around the time of the repeated "CodeLensFactory" lines at the end of the log. Nothing other actions show up in the log once in this "disconnected" state except for the kernel restart request.
(The VSCode version pasted below is 1.95.3, but I get the same behavior with 1.96.0 and 1.96.2. I was also using 2024.11.0 of the extension then and still had the problem.)
VS Code Version
Version: 1.95.3 Commit: f1a4fb101478ce6ec82fe9627c43efbf9e98c813 Date: 2024-11-13T14:50:04.152Z Electron: 32.2.1 ElectronBuildId: 10427718 Chromium: 128.0.6613.186 Node.js: 20.18.0 V8: 12.8.374.38-electron.0 OS: Linux x64 6.6.64
Jupyter Extension Version
2024.10.0
Jupyter logs
Coding Language and Runtime Version
No response
Language Extension Version (if applicable)
No response
Anaconda Version (if applicable)
No response
Running Jupyter locally or remotely?
Remote
The text was updated successfully, but these errors were encountered: