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
Happy to contribute this to nteract. Feedback appreciated.
Is your feature request related to a problem? Please describe.
Currently it looks like the "ok" | "aborted" | "error" status from the kernel on cell execution is not being raised during cell execution along with update_cell_status or updating execution counts.
While information on the success or failure of the cell execution can be interpreted by the execution of the cell and the status, it will be more deterministic to provide the information coming directly from the kernel.
Describe the solution you'd like
Raise an action on cell execution on the cell execution result on CELL_EXECUTION_SUCCESS ("ok") | CELL_EXECUTION_FAILED ("error") | CELL_EXECUTION_ABORTED ("aborted")
The text was updated successfully, but these errors were encountered:
Happy to contribute this to nteract. Feedback appreciated.
Is your feature request related to a problem? Please describe.
Currently it looks like the "ok" | "aborted" | "error" status from the kernel on cell execution is not being raised during cell execution along with update_cell_status or updating execution counts.
This is part of the messaging protocol that is coming directly from the kernel which is helpful to understand what happened to the execution on the kernel. https://jupyter-client.readthedocs.io/en/stable/messaging.html#execution-results
While information on the success or failure of the cell execution can be interpreted by the execution of the cell and the status, it will be more deterministic to provide the information coming directly from the kernel.
Describe the solution you'd like
Raise an action on cell execution on the cell execution result on CELL_EXECUTION_SUCCESS ("ok") | CELL_EXECUTION_FAILED ("error") | CELL_EXECUTION_ABORTED ("aborted")
The text was updated successfully, but these errors were encountered: