bazel-contrib / bazel-contrib/vscode-bazel

Starting debugger should re-run starlark code

Open
#443 0 comments 2 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
296
Forks
108
Avg merge
3d 22h
Merged PRs (30d)
5

Description

If you start debugging a target that you've built before, no breakpoints are hit. I guess right now you just have to manually `bazel shutdown` every time you start debugging? It seems like the debugger should do this automatically at the start of a debug session as I don't see the use in starting a debug session that is guaranteed to not hit any breakpoints.

Contributor guide

Open the contributing guide

Research direction

Trace the VS Code debugger start flow and the Bazel shutdown behavior described in the issue. Reproduce the case with a previously built target and a breakpoint, then verify that starting a debug session reruns the relevant Starlark code and reaches the breakpoint without requiring manual bazel shutdown.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
build-system, devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.