Bugfix / Errors when triggering restart kernel and run all cells

[truongle1501]

Issue Description

When triggering “Restart kernel and run all cells”, both jupyter-server-nbmodel and jupyter-client show incorrect behavior:

1. Early cell execution stop

• Re-triggering Restart kernel and run all cells while the notebook is already executing (e.g., 2nd or 3rd run) causes execution to stop prematurely.
• Root cause: jupyter-client stops cell execution too early.
• Related fix: jupyter-client PR #1069
• After applying this fix, jupyter-server-nbmodel’s kernel worker queue does not explicitly clear in-queue tasks when a task reply has status=error. As a result, old tasks sometimes remain in the queue.

2. Error during kernel startup

• If a user triggers cell execution while the kernel is still in the starting (connecting) state, an error occurs:

  Got events for closed stream <zmq.eventloop.zmqstream.ZMQStream object at 0x112bb66e0>
  

[github-actions]

👈 Launch a Binder on branch truongle1501/jupyter-server-nbmodel/fix%2Frestart-kernel-and-run-all-cells