-
Notifications
You must be signed in to change notification settings - Fork 290
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
Wrong elapsed time reported #12399
Comments
Thanks, I believe we've encountered this in the past, its due to network latency. We could start the timer when we get the first packet for the request (however this would still have the same issue as we might be slow/busy processing other messages when the execution has completed) |
@joaomoreno
Basically I would like to see how long different parts of the extension take to run. |
@DonJayamanne Here's the notebook which reproduces it: https://github.com/joaomoreno/aoc2022/blob/main/13/13.ipynb You can fork this repo, install Jupyter and Python and open the notebook against the |
@joaomoreno Thanks for the info, I've done the same thing, and opened in github codespaces desktop (which is what I believe you are using) Please could your provide the following two:
|
Jupyter Output
|
@joaomoreno
Also, does the timer start from 0 and then gradually go to 37s, or does the timer start half way. |
Besides network latency, a busy extension host can also cause this, so the installed extensions might be relevant. trace-level VS Code window logs can also tell us what happened on vscode's side. I will try to repro it. |
The timer started half way. I did not do any post processing of the recording. I also can't repro today, feel free to close. |
Closing based on the following two messages |
fwiw I also finally got my 130 extensions installed and can't repro the issue. But probably some extension was hogging the EH cpu when this happened. |
Well it happened many times. Pretty much every day in December, as this was my Advent of Code repo and my notebooks all had that problem. |
Thanks for selfhosting notebooks! If you see it again please grab logs and check EH CPU. I'll watch for it too. |
i've been getting the exact same behavior as the OP, but my timer starts at 41.2 seconds on every cell, and then reports the correct run time once it completes |
Applies To
What happened?
When I press play on this cell, the elapsed time is ~24 seconds off.
VS Code Version
1.75.0-insider
Jupyter Extension Version
v2023.1.1003441034
Jupyter logs
Coding Language and Runtime Version
Python 3.9.15
Language Extension Version (if applicable)
v2022.21.13481008
Anaconda Version (if applicable)
No response
Running Jupyter locally or remotely?
None
The text was updated successfully, but these errors were encountered: