https://dagster.io/ logo
#ask-ai
Title
# ask-ai
p

Peter Mburu

02/21/2024, 6:52 AM
how to add breaking points, when using vs code
s

Scout

02/21/2024, 6:52 AM
To add breakpoints when using Visual Studio Code (VS Code) for debugging your Dagster project, you can follow these general steps: 1. Open your Dagster project in VS Code. 2. Navigate to the file where you want to add a breakpoint. 3. Click in the gutter to the left of the line numbers where you want to pause execution. A red dot will appear, indicating a breakpoint has been set. 4. Configure your
launch.json
file in VS Code to set up the debugging environment. This file tells VS Code how to launch and debug your application. You can access this file by going to the Run and Debug view (Ctrl+Shift+D) and selecting "create a launch.json file" if it doesn't already exist. Here's an example of a
launch.json
configuration for debugging a Dagster project, as mentioned in the documentation:
Copy code
json {     "version": "0.2.0",     "configurations": [         {             "name": "dagster dev",             "type": "python",             "request": "launch",             "module": "dagster",             "args": [                 "dev",             ],             "subProcess": true         }     ] }
5. Start the debugger in VS Code by selecting the appropriate configuration from the Run and Debug dropdown and clicking the green play button or pressing F5. Your code will run, and execution will pause when it hits the breakpoint you set. 6. Once the debugger is paused, you can inspect variables, step through code, and use other debugging features provided by VS Code. Remember that the exact configuration in
launch.json
may vary depending on your specific setup and what you are trying to debug (e.g., a Dagster pipeline, a sensor, or a schedule). The example provided is a starting point, and you may need to adjust the arguments and other settings to match your development environment. If you encounter any issues or need further customization for your debugging setup, you can refer to the VS Code documentation on debugging for more detailed instructions and troubleshooting tips.
8 Views