Skip to content

Conversation

@amoeba
Copy link
Member

@amoeba amoeba commented Sep 16, 2025

It took me some research to find the specific way to run dlv with dbc so this patch documents it.

@amoeba amoeba changed the title docs: Add debugging section to CONTRIBUTING.md docs: add debugging section to CONTRIBUTING.md Sep 16, 2025
Copy link
Member

@zeroshade zeroshade left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is great! Maybe we should also mention that much of the work to handle the dlv server is managed for you automatically if you're using VS Code and the Go extension there

@amoeba
Copy link
Member Author

amoeba commented Sep 17, 2025

This is great! Maybe we should also mention that much of the work to handle the dlv server is managed for you automatically if you're using VS Code and the Go extension there

Just for tests or even for debugging go run ./cmd/dbc? Debugging tests does work out of the box but I was never able to figure out how to debug bubbletea with VS Code so I ended up with this.

@zeroshade
Copy link
Member

if you use a launch.json file you can have it use the debugger directly with a package and args that is the equivalent of go run ./cmd/dbc. Don't think we need to add such an update in this PR though

@amoeba
Copy link
Member Author

amoeba commented Sep 17, 2025

I added a quick first sentence to try to explain that debugging dbc can be done the usual way.

@amoeba amoeba merged commit dc87827 into columnar-tech:main Sep 17, 2025
7 checks passed
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.

2 participants