-
-
Notifications
You must be signed in to change notification settings - Fork 413
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
Kernel exception: usage_request #1091
Comments
Hmm, I don't see There was a PR to add a Looks like it might be a kernel extension? https://github.com/jupyter-server/jupyter-resource-usage I guess we should simply ignore messages we don't understand? |
For example, we could replace Line 8 in 74e3e09
with invokelatest(get(handlers, msg.header["msg_type"], default_handler), socket, msg) where |
We could additionally add support for the https://github.com/jupyter-server/jupyter-resource-usage extension, I guess, similar to how it is handled in Though that would seem to require a Julia equivalent of the Python |
Don't know how these things work but as a first thing maybe just output it to the Jupyter log instead of the cell stderr? (or ofc your suggestion of do nothing) I don't actually use that extension, although looks like the cluster does comes with it preinstalled so that seems like a good theory its that. |
Some more context: we see this on jupyter.nersc.gov -- It's intermittent, and seems to vary over time. Due to this, I thought it might be related to other issues we're having at NERSC. However, based in this new information, I am going to revise my theory: It's possible that this kernel extension was added/changed recently. It makes sense to have something like this on shared nodes. I therefore suggest that:
Ping'ing @rcthomas |
#1092 should work around the immediate issue by ignoring unknown requests. Responding to usage_data requests properly is much more difficult since we don't have the analogue of |
May I ask whether there will be a patch release soon for solving this |
Is #1092 ready to be merged? It would be nice to have a patch release that at least silences these messages. Many thanks! |
On some particular cluster's Jupyterlab, I keep geting these messages periodically in random cells:
Julia installed from binaries, IJulia v1.24.0, Jupyterlab 3.6.5
The text was updated successfully, but these errors were encountered: