Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Busy indicator shows wrong status #13635

Open
davidbrochart opened this issue Dec 21, 2022 · 4 comments
Open

Busy indicator shows wrong status #13635

davidbrochart opened this issue Dec 21, 2022 · 4 comments
Labels

Comments

@davidbrochart
Copy link
Contributor

Description

When running a single cell, the busy indicator sometimes shows a half-filled circle.

busy.mp4

Reproduce

  1. mamba install jupyterlab
  2. pip freeze shows jupyterlab 3.5.2 and ipykernel 6.19.4
  3. Execute a simple time.sleep(1)
  4. Randomly see the wrong busy indicator.

Expected behavior

The busy indicator should show a filled circle when only one cell is executing.

Context

  • Operating System and version: Linux Ubuntu 21.04
  • Browser and version: Google Chrome Version 108.0.5359.124
  • JupyterLab version: 3.5.2
@jupyterlab-probot jupyterlab-probot bot added the status:Needs Triage Applied to new issues that need triage label Dec 21, 2022
@JasonWeill JasonWeill removed the status:Needs Triage Applied to new issues that need triage label Dec 29, 2022
@trungleduc
Copy link
Member

Thanks @davidbrochart for reporting it. The indicator makes an assumption that if two cells are executed consequently and the delay between them is under 1000ms, they are counted as a group of two execution so that you will see a half-filled circle.

state.timeout = window.setTimeout(() => {
state.needReset = true;
}, 1000);

I don't know if 1000ms is too big, we might lower it down to 500ms.

@davidbrochart
Copy link
Contributor Author

This seems very arbitrary and error prone. Shouldn't the kernel status on IOPub be used instead?

@trungleduc
Copy link
Member

trungleduc commented Jan 3, 2023

I count one second after the kernel idle message of the IOPub channel. If we don't have this delay when you manually execute multiple simple cells, the execution status is reset after each cell and we can't count the total cells scheduled.

@davidbrochart
Copy link
Contributor Author

Ah I see, then 1 second is too much IMO, it should be something like 100 ms.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants