Robert Findley

> the first time I clicked "run test" on FuzzTest did go test -run ^FuzzTest$ instead of go test -fuzz ^FuzzTest$ Oops, that's just a bug! Thanks for reporting. @hyangah...

Moving this to the VS Code issue tracker. I don't think this type of workflow is appropriate to run from the language server -- better to invoke the test client...

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`,...

I am not naively able to reproduce this. It would be very suprising if this code broke gopls' intellisense, since gopls is built on top of compiler tools which definitely...

@anirudhgiri indeed, I just installed VS Code 1.86.1 and reproduced, *without even installing the Go extension*. This is a VS Code bug. I've filed it as microsoft/vscode#205306. VS Code 1.86...

I'm going to leave this open for visibility. For now, the workaround is to use `"gopls": { "ui.semanticTokens": true }`.

VS Code Go doesn't support formatOnSaveMode: "modifications". Formatting uses the same logic as [gofmt](https://pkg.go.dev/cmd/gofmt), which operates on whole files at a time. Marking this as a feature request, but it...

@Malix-off I'm not sure. CC @hyangah, who may know.

How recent is your gopls? This may have been https://go.dev/issue/65516.

Duplicate of #3110. This error is only encountered in a very old version of gopls (#1300). Do you possibly have multiple versions of gopls installed?