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
I'm not sure exactly what the issue is but sometimes when I add a remote server, I can't see available kernels. Sometimes, I can see them, but when I select one and try to run a cell, nothing seems to happen. I can't consistently reproduce the issue, otherwise I would open a bug report.
VSCode version 1.74.2
Jupyter extension version v2022.11.1003412109
Setup:
I have a jupyter notebook server running on a remote machine that I create an ssh tunnel to to expose it locally. The notebook server does not require a token. I can access the ui in my web browser like normal.
What I've seen so far:
Things will to be working fine, but if I shut the remote server or kill my ssh tunnel and restart it, vscode doesn't seem to work properly. In VSCode I've tried removing the remote server and reconnecting. It seems to reconnect without error, but can no longer see the kernels on the remote server, only local kernels are listed. Other times I'll see the remote kernels but nothing appears to happen when I select one and try to run cells. Repeating this a few times sometimes gets things to work.
At one point I thought it was because I was including a trailing / in the server url, because using http://localhost:8123/gateway/default/jupyter rather than http://localhost:8123/gateway/default/jupyter/ got things working again. More recently I tried again with the / and it does work, so that's clearly not the issue.
Things are working now but I'll post extension logs if I manage to wind up in a broken state again.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm not sure exactly what the issue is but sometimes when I add a remote server, I can't see available kernels. Sometimes, I can see them, but when I select one and try to run a cell, nothing seems to happen. I can't consistently reproduce the issue, otherwise I would open a bug report.
VSCode version
1.74.2
Jupyter extension version
v2022.11.1003412109
Setup:
I have a jupyter notebook server running on a remote machine that I create an ssh tunnel to to expose it locally. The notebook server does not require a token. I can access the ui in my web browser like normal.
What I've seen so far:
Things will to be working fine, but if I shut the remote server or kill my ssh tunnel and restart it, vscode doesn't seem to work properly. In VSCode I've tried removing the remote server and reconnecting. It seems to reconnect without error, but can no longer see the kernels on the remote server, only local kernels are listed. Other times I'll see the remote kernels but nothing appears to happen when I select one and try to run cells. Repeating this a few times sometimes gets things to work.
At one point I thought it was because I was including a trailing
/
in the server url, because usinghttp://localhost:8123/gateway/default/jupyter
rather thanhttp://localhost:8123/gateway/default/jupyter/
got things working again. More recently I tried again with the/
and it does work, so that's clearly not the issue.Things are working now but I'll post extension logs if I manage to wind up in a broken state again.
Beta Was this translation helpful? Give feedback.
All reactions