Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

diagnostic: add an option for verbose logging of extension's activity #54

Open
hyangah opened this issue May 15, 2020 · 1 comment
Open

diagnostic: add an option for verbose logging of extension's activity #54

hyangah opened this issue May 15, 2020 · 1 comment
Milestone
vscode-go/unplanned

Comments

@hyangah
Copy link
Contributor

hyangah commented May 15, 2020

Originally from microsoft/vscode-go#526

  • underlying command execution
  • changes to file systems, env vars
  • any errors

See Chrome debugging extension's diagnosticLogging
@hyangah hyangah mentioned this issue May 15, 2020
Closed
@hyangah hyangah added this to the On Deck milestone Aug 31, 2020
@hyangah
Copy link
Contributor Author

hyangah commented Feb 17, 2021

we added go.logging.level setting to trace how the go extension chooses the 'go' binary (and GOROOT).
It's currently machine-overridable.
I recently noticed this isn't working for codespaces though. Still need investigation on where to output this.

@hyangah hyangah modified the milestones: On Deck, Backlog Apr 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
vscode-go/unplanned
Development

No branches or pull requests
1 participant
@hyangah