-
Notifications
You must be signed in to change notification settings - Fork 296
Debugging the extension
Rich Chiodo edited this page Oct 16, 2020
·
2 revisions
Generally follow the guidelines in the CONTRIBUTING.md
However there are times where you need to debug what VS code is doing too.
Follow the directions here to get VS code up and running https://github.com/microsoft/vscode/wiki/How-to-Contribute#debugging
Once it builds, you then need to convince the vscode-OSS-dev build to load our extension and debug it.
To do so:
- Find the vscode-oss-dev extensions folder. Example:
C:\Users\Rich\.vscode-oss-dev\extensions
- git clone the jupyter repo into a folder like so at that spot:
git clone https://github.com/microsoft/vscode-jupyter.git ms-toolsai.jupyter-2020.10.0-dev
- Build the jupyter extension at that location
- Launch VS code from the vscode-oss-dev build
- It should load the built jupyter extension
- Breakpoints (for now) can be set in the jupyter extension by setting them in the
out
folder.
- 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