Hyang-Ah Hana Kim

@alandonovan Is it possible to add `go.mod` for this material? Now Module mode is the default and go tools got picky about the lack of go.mod. gopls also gets confused...

Have you tried to retract the module instead? https://pkg.go.dev/about#removing-a-package Just removing it from pkgsite won't affect proxy.golang.org, and it will be still accessible.

@ymolists I don't know how Go extension is related to storage.json (what is that file?) Do you see this issue only if Go extension is enabled?

@ymolists `htop` lists userland threads by default. (shift+H disables it). Assuming you are running multi-core, I think this is normal. (Go runtime uses multiple threads and actively schedule goroutines on...

Thanks for the report. Can you please share the log you see in the gopls output channel and tell us when you observed this popup (e.g. I was updating `gopls`,...

@ssrlive can you enable logging and see if there is any boolean type value among the `env` property in the launch request the extension is sending to the debug adapter?...

@ssrlive Your settings.json has syntax error. `"go.useGoProxyToCheckForToolUpdates": true` shouldn't be an element of `"go.toolsEnvVars"`. This part ``` "go.toolsEnvVars": { "go.useGoProxyToCheckForToolUpdates":true }, ``` should be ``` "go.toolsEnvVars": { }, /* or...

The only setting the extension may automatically added is `"go.useGoProxyToCheckForToolUpdates": true` Since other settings require manual edits, I guess some race occurred while the extension added the setting. 🤷🏽‍♀️ But,...

@polinasok > @[hyangah](https://github.com/hyangah) Is it even right that we pass go.toolsEnvVars intended for Go tools to debuggee? Good point. Since now dlv can process `env` and the extension directly controls...

``` "go.toolsEnvVars": { "gopls.env": { /* This caused an error message very similar to the above one except about objects*/ "GOFLAGS": "-tags=integration unit" }, }, ``` `"go.toolsEnvVars"` expects string type...