We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
IRkernel
IRdisplay
repr
My team deploys IRkernel 1.3.1 as remote kernels for a Jupyter-compatible notebook webapp.
We install it in a Docker image with IRkernel::installspec(user = FALSE).
IRkernel::installspec(user = FALSE)
Our architecture implements implements the Messaging protocol here for communicating with Jupyter kernels.
The issue we encounter is in interrupting the kernels. We send the interrupt_request message type to the remote kernel via the CONTROL channel. This works well for ipykernel, but not at all for IRkernel.
interrupt_request
Digging into the code for v1.3.1 I see that the kernel handles only one message in the CONTROL channel, shutdown_request.
shutdown_request
It would be nice if IRkernel could handle the interrupt_request message type the same way it does with SIGINT.
This might be related to this issue with Jupyter Notebook #677
And implementation could be similar to #704 for kernel_info_request.
kernel_info_request
The text was updated successfully, but these errors were encountered:
No branches or pull requests
IRkernel
,IRdisplay
, andrepr
IRkernel/repr or a third party repository
My team deploys IRkernel 1.3.1 as remote kernels for a Jupyter-compatible notebook webapp.
We install it in a Docker image with
IRkernel::installspec(user = FALSE)
.Our architecture implements implements the Messaging protocol here for communicating with Jupyter kernels.
The issue we encounter is in interrupting the kernels. We send the
interrupt_request
message type to the remote kernel via the CONTROL channel. This works well for ipykernel, but not at all for IRkernel.Digging into the code for v1.3.1 I see that the kernel handles only one message in the CONTROL channel,
shutdown_request
.It would be nice if IRkernel could handle the
interrupt_request
message type the same way it does with SIGINT.Related
This might be related to this issue with Jupyter Notebook #677
And implementation could be similar to #704 for
kernel_info_request
.The text was updated successfully, but these errors were encountered: