Jupyter lab status bar is showing that the kernel is idle even though the kernel is busy as seen in the top right kernel status tab. This occurs when we switch between an idle notebook and a busy notebook.
Reproduce
Create a new notebook named notebook_1.ipynb. Add a long running script in a cell and execute the same.
Create a second notebook named notebook_2.ipynb. Assign a kernel and wait until kernel is idle.
Switch between notebook_1.ipynb and notebook_2.ipynb.
Check status bar of notebook_1.ipynb. Kernel status will be shown as idle instead of busy.
Expected behaviour
Kernel status of busy notebook should be shown as busy instead of idle.
Context
Operating System and version: macOS Monterey, version 12.6.4
Original issue was opened as jupyterlab/jupyterlab#14578. Migration requested by brijsiyag
IOpub messages received twice with alternate execution_state as idle and busy. This leads to the inconsistent behaviour.
I commented on the original issue in JupyterLab. I don't think this is a problem with ipykernel; rather, JupyterLab is not properly handling IOPub status messages from multiple channels in the client.
Description
Jupyter lab status bar is showing that the kernel is idle even though the kernel is busy as seen in the top right kernel status tab. This occurs when we switch between an idle notebook and a busy notebook.
Reproduce
Expected behaviour
Kernel status of busy notebook should be shown as busy instead of idle.
Context
package versions
https://github.com/jupyterlab/jupyterlab/assets/6435143/46594eec-75e3-4fcb-9ece-4b25360dedbd
Original issue was opened as jupyterlab/jupyterlab#14578. Migration requested by brijsiyag IOpub messages received twice with alternate execution_state as
idle
andbusy
. This leads to the inconsistent behaviour.