vscode-jupyter: VS Code select Existing Jupyter Server stopped working
Environment data
- VS Code version: 1.79
- Jupyter Extension version (available under the Extensions sidebar): v2023.5.1001582324
- Python Extension version (available under the Extensions sidebar): v2023.10.1
- OS (Windows | Mac | Linux distro) and version: Linux Debian Buster
- Python and/or Anaconda version: Python 3.8.12
- Type of virtual environment used: venv
- Jupyter server running: Remote
Expected behaviour
Until this week, when I upgraded to VS Code 1.79 and latest Jupyter extension, I would typically SSH attach my VS code window to a remote machine and use a running jupyter kernel there. To do so, I’d use Jupyter: Create Interactive Window
, then click on the kernel select, do Select Another Kernel
, then Existing Jupyter Server
, at which point i’d enter the URI and token of the server. At that point it would show me the available Python kernel to select and I’d click it.
Actual behaviour
After typing in the URI of the server, I either just get to the window that says ‘Select Kernel’ and the little blue processing bar bounces back and forth until it times out, or I see a screenshot like the one attached below which directs me to check the connecting from vs code dev link and shows that the error is ENETUNREACH, which I can’t interpret. However, as recommended in that article, I was able to confirm that I can port forward the running jupyter kernel to my local machine and view it in the browser and execute code. So, it seems the kernel is working just fine, but VS Code can’t communicate with it for one reason or another.
Logs
About this issue
- Original URL
- State: closed
- Created a year ago
- Reactions: 3
- Comments: 21 (12 by maintainers)
I encountered the same issue and rolling back the Jupyter extension to
v2023.4.*
did the trick for me.Temporary work around
We’re sorry for the inconvenience caused by this issue, As a temporary solution please try the following:
Jupyter: Clear Jupyter Remote Server List
This should allow you to use remote Jupyter servers with the latest version. Optionally you can try VS Code Insiders and the latest pre-release version of the Jupyter extesnion.
Thanks for this @mcitoler … your suggestion of rolling back to 2023.4.x also fully resolved the issue for me!
I was having same issue as described in this thread and had tried installing all of the versions of 2023.5.x and 2023.6.x available on https://marketplace.visualstudio.com/items?itemName=ms-toolsai.jupyter > Version History, but had same issue.
I went into VS Code > Extension > Uninstall dropdown > Install Another Version, chose the 2023.4 option, downloaded the VSIX, and installed it. Now the issue is resolved!
@mcitoler @TekeDado Please could you help me figure out the problem by installing the following two VSIX
Please could you share a sample of the URL that you paste into the textbox. You can remove the server name/ip address and token.
Note: When uploading the logs, you might want to strip the server name and the token (please ensure you replace with a string such as
<serverName>
,<token>
, this way I know you have replaced them your self.2023.4 (from marketplace)
Jupyter: Show Output
and copy the output from the output panel(Tip: The output panel is displayed at the bottom , where the terminal is displayed, and you can also get to it using the command
View: Toggle Output
and then select the optionJupyter
from the dropdown list displayed at the top right of the output panel)First VSIX (should fail)
Extensions: Install from VSIX
) ms-toolsai-jupyter-insiders.vsix (2).zipSecond VSIX (should work)
The logs will help me determine the difference between the versions Please do send all of the logs.
thank you for your patience and help here.