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
Recording execution timings seems to break notebook #8056
Labels
status:resolved-locked
Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion.
Comments
jasongrout
added a commit
to jasongrout/jupyterlab
that referenced
this issue
Mar 19, 2020
Returning false prevents the message from being processed by the future or by any other hook, which messes everything up. Fixes jupyterlab#8056
I reproduced this with stock jlab 2.0.1 as well. |
saulshanabrook
pushed a commit
that referenced
this issue
Mar 30, 2020
Returning false prevents the message from being processed by the future or by any other hook, which messes everything up. Fixes #8056
jasongrout
added a commit
to jasongrout/jupyterlab-execute-time
that referenced
this issue
Apr 8, 2020
There was a bug in JLab 2.0.0 and 2.0.1 that prevented cell execution when recordTiming was enabled. You might be able to cut down on support issues if you just go ahead and require at least JLab 2.0.2. See jupyterlab/jupyterlab#8057 and jupyterlab/jupyterlab#8056
mlucool
pushed a commit
to deshaw/jupyterlab-execute-time
that referenced
this issue
Apr 9, 2020
There was a bug in JLab 2.0.0 and 2.0.1 that prevented cell execution when recordTiming was enabled. You might be able to cut down on support issues if you just go ahead and require at least JLab 2.0.2. See jupyterlab/jupyterlab#8057 and jupyterlab/jupyterlab#8056
lock
bot
added
the
status:resolved-locked
Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion.
label
Apr 25, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
status:resolved-locked
Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion.
Description
When I set the recordTimings option to be true with
in the user preferences for the notebook, the "execution timings" get outputted to the cell metadata, but the kernel doesn't seem to actually execute the cell. For example, print("hello world!") won't print,
1+1
won't output2
, and the cell reports jibberish as having evaluated normally instead of causing an error.Reproduce
recordTiming
to be true and saveExpected behavior
Notebook should run normally when execution timings are active.
Context
Troubleshoot Output
Command Line Output
Browser Output
The text was updated successfully, but these errors were encountered: