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
#29 implements timing of cell execution, but not of when cell execution was scheduled. This can be done by recording the current time when the task to execute the request is put on the task queue, here:
For backward compatibility this should be recorded as iopub.status.busy. This will allow extensions such as jupyterlab-execute-time to display the time since the server-side execution was scheduled (as they do for normal execution).
The text was updated successfully, but these errors were encountered:
#29 implements timing of cell execution, but not of when cell execution was scheduled. This can be done by recording the current time when the task to execute the request is put on the task queue, here:
jupyter-server-nbmodel/jupyter_server_nbmodel/handlers.py
Line 569 in 535e241
or more precisely here:
jupyter-server-nbmodel/jupyter_server_nbmodel/handlers.py
Line 503 in 535e241
For backward compatibility this should be recorded as
iopub.status.busy
. This will allow extensions such asjupyterlab-execute-time
to display the time since the server-side execution was scheduled (as they do for normal execution).The text was updated successfully, but these errors were encountered: