Skip to content
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

IRkernel does not handle interrupt_message control message #727

Open
3 of 4 tasks
ahjota opened this issue Jan 12, 2023 · 0 comments
Open
3 of 4 tasks

IRkernel does not handle interrupt_message control message #727

ahjota opened this issue Jan 12, 2023 · 0 comments

Comments

@ahjota
Copy link

ahjota commented Jan 12, 2023

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.

@ahjota ahjota changed the title IRkernel does not handle kernel_interrupt mesage IRkernel does not handle interrupt_message control message Jan 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant