-
Notifications
You must be signed in to change notification settings - Fork 293
Errors that code can throw
Rich Chiodo edited this page Jul 29, 2022
·
9 revisions
All of the errors thrown in the Jupyter extension that aren't unexpected should have a distinct class.
Example:
Each error should list:
- Cause - what would cause this error to be thrown
- Handled by - how the error is handled. This might be something like shown to the user or put in a cell or swallowed.
The list of errors is pretty easy to find by searching:
That will also show throw new Error
cases, but those are generally for unexpected conditions.
- Contribution
- Source Code Organization
- Coding Standards
- Profiling
- Coding Guidelines
- Component Governance
- Writing tests
- Kernels
- Intellisense
- Debugging
- IPyWidgets
- Extensibility
- Module Dependencies
- Errors thrown
- Jupyter API
- Variable fetching
- Import / Export
- React Webviews: Variable Viewer, Data Viewer, and Plot Viewer
- FAQ
- Kernel Crashes
- Jupyter issues in the Python Interactive Window or Notebook Editor
- Finding the code that is causing high CPU load in production
- How to install extensions from VSIX when using Remote VS Code
- How to connect to a jupyter server for running code in vscode.dev
- Jupyter Kernels and the Jupyter Extension