-
Notifications
You must be signed in to change notification settings - Fork 293
Errors that code can throw
Rich Chiodo edited this page Jul 28, 2022
·
9 revisions
The table below lists all of the specific errors we throw in the Juptyer extension's code, what causes each error, and how each error is handled.
Error Location | What causes the error | How is it handled |
---|---|---|
InteractiveCellResultError | Kernel gets an error when executing a cell | Bubbles up inside the InteractiveWindow or CodeWatcher in order to indicate which cell had an error. Basically lets an error come out to the correct cell in the InteractiveWindow because the last cell isn't the one that caused the error (if multiple are queued) |
JupyterDebuggerNotInstalledError | Thrown when we can't load debugpy into the interactive window's kernel. | Shown to the user in a cell's output that they tried to debug |
- 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