We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
1 parent e584fdb commit 3ec870bCopy full SHA for 3ec870b
80-kernel-info/kernel-info.md
@@ -3,7 +3,7 @@
3
## Problem
4
5
When connecting a new websocket to an existing kernel via the Jupyter server, if the kernel execution is
6
-stopped on a breakpoint, the messages sent over the websocket get no reply. This is because when
+busy (e.g. long running cell) or stopped (e.g. on a breakpoint), the messages sent over the websocket get no reply. This is because when
7
establishing a new websocket connection, the Jupyter server will send `kernel_info` requests to the kernel
8
and will prevent sending any other request until it receives a `kernel_info` reply. Since the `kernel_info`
9
request is sent on the shell channel and the kernel execution is stopped, it cannot reply to that request.
0 commit comments