You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found this issue when I was trying to debug on a remote kernel, due to the network latency, the UI need some time to change debug status after user click "continue" button, so the user have chance to click "continue" for several times. If there is only one breakpoint in the code cell, the kernel only expect for accept one "continue" command, when the extra (second in this case) "continue" command send to kernel, kernel stucked and stop to response.
version:
ipykernel 6.22.0
platform:
windows
note:
"next" command don't have this issue
The text was updated successfully, but these errors were encountered:
I found this issue when I was trying to debug on a remote kernel, due to the network latency, the UI need some time to change debug status after user click "continue" button, so the user have chance to click "continue" for several times. If there is only one breakpoint in the code cell, the kernel only expect for accept one "continue" command, when the extra (second in this case) "continue" command send to kernel, kernel stucked and stop to response.
version:
ipykernel 6.22.0
platform:
windows
note:
"next" command don't have this issue
The text was updated successfully, but these errors were encountered: