-
Notifications
You must be signed in to change notification settings - Fork 300
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
Unable to start kernel - Waiting for Jupiter Session to be Idle (Kernel fails to start as completions request crahes without sending a response back) #9014
Comments
Thanks for filing this issue.
Also are you trying to connect to an existing kernel with active connections or are you starting a whole new session?
The message with zmq can be ignored. |
This comment was marked as outdated.
This comment was marked as outdated.
I can report the same issue on OSX. |
@panxnan @jcn2185 @JorisDeRidder
|
I was experiencing same issue "[Remote Server: Waiting for Jupiter Session to be Idle]" |
The Jupyter output panel indeed lists an error caused by Jedi (see below). Although it will affect the autocompletion, I'm not sure it also causes the eternal "Waiting for Jupyter session to be idle". The output log explicitly mentions that it set the status to idle. In any case, I don't see how to downgrade jedi without rendering the entire conda environment inconsistent.
|
@JorisDeRidder |
@JorisDeRidder please install the latest pre-release version of the jupyter extension and it should work. |
Problem solved! Wonderful, many thanks! |
I'm having the same error on Ubuntu 20.04. I've set the jupyter extension version to pre-release but the error persists and now code keeps telling me that I need to install ipykernel(it's already installed, manually through pip and selecting the code prompt). Code version is 1.65.0, installed through snap and python version is 3.8.10 64 bit. Full log
|
Alright so this one surprised me a little.. I was using Jupyter code cells. And I ran also ran into the "Waiting for Jupiter Session to be Idle" issue. Even a reboot of my machine did not help. However, the error disappeared when I renamed my file, from "inspect.py" to "tmp.py". |
Same issue here on Ubuntu 20.04.
|
Also just started running into this again on OS X in the last couple days... @DonJayamanne, would you like a new issue opened? |
Hi, same issue here with M1, changing to pre release version doesn't solve it |
Yes, please create a new issue. |
is it fixed? |
@crystalchengyafeng Please file an issue and ping me and i'll look into it. this issue has been fixed. |
Applies To
What happened?
First of all - thank you so much for making this extension!
Expected: I run docker container
tensorflow/tensorflow:2.6.0-gpu-jupyter
on my server that has a GPU, since I am connecting from a M1 Mac. I have used this for weeks without issue. I would connect to the server with IP + token and the system would just work.Actually:
Connecting to kernel: Python 3: Waiting for Jupiter Session to be idle
. This message stays up for hours even.(Remote)
next to the kernel name, so I'm not sure if now my system and the server's kernels are getting confused?Anyways, I pasted the Jupyter extension logs below. To help explain the logs better and put a few character returns in for easier reading.
VS Code Version
Version: 1.64.2 (Universal) Commit: f80445acd5a3dadef24aa209168452a3d97cc326 Date: 2022-02-09T22:00:58.347Z Electron: 13.5.2 Chromium: 91.0.4472.164 Node.js: 14.16.0 V8: 9.1.269.39-electron.0 OS: Darwin arm64 20.6.0
Jupyter Extension Version
v2022.1.1201831736
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: