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

DM-40143: Adopt new notebook execution result with error field #61

Merged
merged 13 commits into from
Jan 4, 2024

Conversation

jonathansick
Copy link
Member

@jonathansick jonathansick commented Jan 3, 2024

The notebook execution extension from rsp-jupyter-extensions now returns the notebook even if an execption was raised while executing the notebook. As well, the extension now returns a JSON object with fields:

  • notebook (the executed ipynb)
  • resources (the resources dictionary)
  • error (structured information about the exception raised, or null)

The result of error is now made available from the GET /notebooks/:job_id endpoint under the new ipynb_error field.

This PR also adds a tutorial in the user guide on how to use Noteburst's API.

This command is no longer included in tox.ini
Use backtracking resolver and add a update-deps-no-hashes target for
development against git-based dependencies.
The execution endpoint provided by jupyterlab utils has changed; if an
exeception is triggered by a notebook execution then the notebook will
still be returned. Additionally, the exception information is included
in an error field.

The NotebookResponse model now includes this information in an
ipynb_error field that includes:

- traceback string
- exeception name
- exception message
The original @validator is deprecated
The traceback and message end up being the same; so we'll only show the
"message" for now. We can re-add the "traceback" later if we find it
does contain more information.
@jonathansick jonathansick merged commit 466e8c6 into main Jan 4, 2024
4 checks passed
@jonathansick jonathansick deleted the tickets/DM-40143 branch January 4, 2024 22:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant