Skip to content
Snippets Groups Projects
Select Git revision
  • c6ceee34a7ed5304cd82e1ea317cc22b382f60f8
  • master default protected
  • exec_auto_adjust_trace
  • let_variables
  • v1.4.1
  • v1.4.0
  • v1.3.0
  • v1.2.0
  • v1.1.0
  • v1.0.0
10 results

prob2-jupyter-kernel

  • Open with
  • Download source code
  • Your workspaces

      A workspace is a virtual sandbox environment for your code in GitLab.

      No agents available to create workspaces. Please consult Workspaces documentation for troubleshooting.

    • user avatar
    Run commands in a separate executor instead of the main kernel thread
    dgelessus authored 
    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
    History
    user avatar c6ceee34
    History
    Name Last commit Last update