vscode: add a script to generate debugger config#12917
vscode: add a script to generate debugger config#12917lizan merged 5 commits intoenvoyproxy:masterfrom
Conversation
Signed-off-by: Lizan Zhou <lizan@tetrate.io>
|
cc @davinci26 |
snowp
left a comment
There was a problem hiding this comment.
Thanks, just one suggestion
oschaaf
left a comment
There was a problem hiding this comment.
Nice! Some drive by comments feel free to ignore. Also, out of scope, but I wonder if it is possible and what it would take to pre-generate a populated picker list based on this with all targets
That probably need to be a VS Code extension... |
|
Some of the folks involved with @envoyproxy/windows-dev or @rmiller14 may be knowledgeable in this subject. |
snowp
left a comment
There was a problem hiding this comment.
Just one nit, otherwise LGTM
|
|
||
|
|
||
| def getExecutionRoot(workspace): | ||
| # If compilation database exists, use its execution root |
There was a problem hiding this comment.
Explaining why the comp db execution root is preferred might be nice
|
/retest |
|
Retrying Azure Pipelines, to retry CircleCI checks, use |
Commit Message:
Additional Description:
Risk Level: Low
Testing: local
Docs Changes: Added
Release Notes: N/A