Snippets Groups Projects

CHANGELOG.md

4 years ago

Run commands in a separate executor instead of the main kernel thread · c6ceee34

dgelessus authored 4 years ago

This fixes a bug where interrupting a command would terminate the main
event loop thread, causing the kernel to stop responding. This happened
because the interrupt handling sent a Java interrupt to the thread
executing the current command, which was always the main event loop
thread. Now commands are executed on a separate executor, which can
safely have Java interrupts sent to it without affecting any
jupyter-jvm-basekernel threads.

c6ceee34

Run commands in a separate executor instead of the main kernel thread

dgelessus authored 4 years ago

This fixes a bug where interrupting a command would terminate the main
event loop thread, causing the kernel to stop responding. This happened
because the interrupt handling sent a Java interrupt to the thread
executing the current command, which was always the main event loop
thread. Now commands are executed on a separate executor, which can
safely have Java interrupts sent to it without affecting any
jupyter-jvm-basekernel threads.

Code owners

Assign users and groups as approvers for specific file changes. Learn more.

To find the state of this project's repository at the time of any of these versions, check out the tags.