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 noticing that some notebooks finish executing server side, while the front end hasn't received anything (stays on the spinner and continues sending the heartbeat). Eventually the kernel is culled due to inactivity and the front end believes the kernel died erroneously because of that. I've tried increasing kernel polling/culling timeouts, but it seems that if it's missed it's missed. Server side these logs look the same, except for when next the front end runs the heartbeat:
b'[Voila] Kernel shutdown: 50d767d5-22b1-4bde-9d52-80a2a8679cf7\n'
b'[Voila] ERROR | Kernel died while waiting for execute reply.\n'
b"[Voila] ERROR | Error at server while executing cell: ...
I'm not sure why it would say there's a server side error though despite the execution finishing above and the kernel going idle.
I should also mention this is very inconsistent, even for a specific notebook. Some notebooks never have this error, some sometimes, and others frequently (still not 100% of the time though). Which to me says something is behaving incorrectly with the async part.
Context
voila version 0.5.5
Operating System and version: Ubuntu 20.04
Browser and version: Firefox 123.0, Chrome 122.0.6261.57
[Voila] Looking for voila in /etc/jupyter
[Voila] Looking for voila in /usr/local/etc/jupyter
[Voila] Looking for voila in /opt/conda/etc/jupyter
[Voila] Looking for voila in /home/voila-runner/.local/etc/jupyter
[Voila] Looking for voila in /home/voila-runner/.jupyter
[Voila] Looking for voila in /home/voila-runner
[Voila] using template: lab
[Voila] template paths:
/opt/conda/share/jupyter/voila/templates/lab
/opt/conda/share/jupyter/nbconvert/templates/lab
/opt/conda/share/jupyter/voila/templates/base
/opt/conda/share/jupyter/nbconvert/templates/base
/home/voila-runner/.local/share/jupyter
/home/voila-runner/.local/share/jupyter/voila/templates
/home/voila-runner/.local/share/jupyter/nbconvert/templates
/opt/conda/share/jupyter
/opt/conda/share/jupyter/voila/templates
/opt/conda/share/jupyter/nbconvert/templates
/usr/local/share/jupyter
/usr/local/share/jupyter/voila/templates
/usr/local/share/jupyter/nbconvert/templates
/usr/share/jupyter
/usr/share/jupyter/voila/templates
/usr/share/jupyter/nbconvert/templates
[Voila] static paths:
/home/voila-runner/.local/share/jupyter/voila/templates/lab/static
/home/voila-runner/.local/share/jupyter/nbconvert/templates/lab/static
/opt/conda/share/jupyter/voila/templates/lab/static
/opt/conda/share/jupyter/nbconvert/templates/lab/static
/usr/local/share/jupyter/voila/templates/lab/static
/usr/local/share/jupyter/nbconvert/templates/lab/static
/usr/share/jupyter/voila/templates/lab/static
/usr/share/jupyter/nbconvert/templates/lab/static
/home/voila-runner/.local/share/jupyter/voila/templates/base/static
/home/voila-runner/.local/share/jupyter/nbconvert/templates/base/static
/opt/conda/share/jupyter/voila/templates/base/static
/opt/conda/share/jupyter/nbconvert/templates/base/static
/usr/local/share/jupyter/voila/templates/base/static
/usr/local/share/jupyter/nbconvert/templates/base/static
/usr/share/jupyter/voila/templates/base/static
/usr/share/jupyter/nbconvert/templates/base/static
/opt/conda/lib/python3.9/site-packages/jupyter_server/static
[Voila] Using /tmp to store connection files
[Voila] Storing connection files in /tmp/voila_x3bk1n9n.
[Voila] Serving static files from /opt/conda/lib/python3.9/site-packages/voila/static.
[Voila] serving directory: '/home/voila-runner'
[Voila] Voilà is running at:
http://localhost:8866/
[Voila] WARNING | No web browser found: could not locate runnable browser.
Browser Output
Ok, voila is still executing... (x10)
GET /api/kernels/ 404
Plugin '@jupyter-widgets/jupyterlab-manager:base-2.0.0' failed to activate.
Error: The model for kernel id 50d767d5-22b1-4bde-9d52-80a2a8679cf7 does not exist
Plugin '@jupyter-widgets/jupyterlab-manager:controls-2.0.0' failed to activate.
Error: The model for kernel id 50d767d5-22b1-4bde-9d52-80a2a8679cf7 does not exist
...
The text was updated successfully, but these errors were encountered:
Thanks @trungleduc - I took the simplified notebook you posted in that issue and I can see it seems to be the same issue. It's not consistent 100% of the time, that's also in line with the notebooks I'm testing as well. But the logs and error seem to match the notebooks I'm struggling with, so I'm willing to bet it's the same issue.
I'll close this one out then and keep an eye on the issue you linked.
Description
I'm noticing that some notebooks finish executing server side, while the front end hasn't received anything (stays on the spinner and continues sending the heartbeat). Eventually the kernel is culled due to inactivity and the front end believes the kernel died erroneously because of that. I've tried increasing kernel polling/culling timeouts, but it seems that if it's missed it's missed. Server side these logs look the same, except for when next the front end runs the heartbeat:
I'm not sure why it would say there's a server side error though despite the execution finishing above and the kernel going idle.
I should also mention this is very inconsistent, even for a specific notebook. Some notebooks never have this error, some sometimes, and others frequently (still not 100% of the time though). Which to me says something is behaving incorrectly with the async part.
Context
Troubleshoot Output
Command Line Output
Browser Output
The text was updated successfully, but these errors were encountered: