-
Notifications
You must be signed in to change notification settings - Fork 293
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
Error: Timed out waiting to get a heartbeat from kernel process #8182
Comments
The root cause of the problem is you don't have ipython_genutils installed. How did you install ipykernel? See this bug here: |
Interesting, thanks. I installed ipykernel after a prompt from VSCode (this was a fresh virtual environment). I haven't come across ipython_genutils before - I'll try installing that and will report back. |
@DonJayamanne it looks like we might be hitting the ipython_genutils issue with Venvs too :( |
@philipnye Please could you activate your virtual environment and type in |
Thanks @rchiodo @DonJayamanne. This is the output from running
After installing ipython_genutils I still the original error: Timed out waiting to get a heartbeat from kernel process. But this is my new Jupyter log:
|
@philipnye
|
Thanks @DonJayamanne. This is my log from the latest VSCode Insiders build:
If I've done it right, running If instead I do Thanks again. |
|
Ah, sorry.
Thanks, Don. |
Thanks for the information.
|
Thanks. That seems to install fine, and running |
Hi @DonJayamanne. Sorry to be resurrecting this, but today I'm getting the error again. Running My logs are as follows:
|
I suspect it had something to do with the fact that it's running on as separate drive (hence the intermittent failures). Is it on a USB or network drive? (
|
Thanks, Don. You're correct in thinking that the U: drive is a network drive that I'm accessing via a firewall. Using an interpreter on my C: drive works successfully. (The latest VSCode Insiders doesn't, using the interpreter in my venv.) |
Thanks for the feedback. I believe the issue is because of the firewall. We spawn a process that's on a network drive and 5 sockets are opened against that process. I'm going to close this issue as this is an environmental issue and things work as expected Regen thinking on a local drive. |
Hi, I'm new to python and want to run my code. @DonJayamanne I'm facing this issue |
Issue Type: Bug
Steps taken:
My log can be found below.
This is an issue that seems to happen intermittently. I previously raised it as #7863, but closed the issue as I thought it was fixed when I moved to VSCode 1.61.0. But I'm experiencing it again.
Following @DonJayamanne's advice, I've tried installing the insiders build and have received the same error there.
VSCode details
Extension version: 2021.10.1001414422
VS Code version: Code 1.62.0 (b3318bc0524af3d74034b8bb8a64df0ccf35549a, 2021-11-03T15:23:01.379Z)
OS version: Windows_NT x64 10.0.19041
Restricted Mode: No
VSCode insiders build details
Version: 1.63.0-insider (user setup)
Commit: 552af97a0170b43c9323bec62211feb184da9749
Date: 2021-11-05T05:16:20.583Z
Electron: 13.5.1
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.19041
VSCode Jupyter log
VSCode insiders build Jupyter log
System Info
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
rasterization: enabled
skia_renderer: enabled_on
video_decode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
A/B Experiments
The text was updated successfully, but these errors were encountered: