-
Notifications
You must be signed in to change notification settings - Fork 350
Fix interrupt_request to use control channel instead of shell #17144
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
base: main
Are you sure you want to change the base?
Conversation
When interrupt_mode is 'message', send interrupt_request on the control channel as specified by Jupyter protocol. This prevents the interrupt from being queued behind pending shell messages.
|
@mntss please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
When interrupt_mode is 'message', send interrupt_request on the control channel as specified by Jupyter protocol. This prevents the interrupt from being queued behind pending shell messages.
Fixes #17143