vscode error: unknown flag: --print-issued-lines

[adamk33n3r]

Talked about in #5640 but I'm getting the above error with even the pre-release build of the extension.

The version I have installed through chocolatey is (devel)

PS C:\ProgramData\chocolatey> go version -m C:\ProgramData\chocolatey\lib\golangci-lint\tools\golangci-lint-2.1.6-windows-amd64\golangci-lint.exe
C:\ProgramData\chocolatey\lib\golangci-lint\tools\golangci-lint-2.1.6-windows-amd64\golangci-lint.exe: go1.24.2
        path    github.com/golangci/golangci-lint/v2/cmd/golangci-lint
        mod     github.com/golangci/golangci-lint/v2    (devel)

And here is some other requested information

PS > code --version
1.100.2
848b80aeb52026648a8ff9f7c45a9b0a80641e2e
x64

PS > code --list-extensions --show-versions | grep 'golang.go@'
[email protected]

PS > golangci-lint.exe --version
golangci-lint has version 2.1.6 built with go1.24.2 from eabc2638 on 2025-05-04T15:41:19Z

PS > go version
go version go1.24.3 windows/amd64

[ldez]

The path is not the same as #5640 (comment)

• C:\ProgramData\chocolatey\bin\golangci-lint.exe
• C:\ProgramData\chocolatey\lib\golangci-lint\tools\golangci-lint-2.1.6-windows-amd64\golangci-lint.exe

Could you explain why?

[adamk33n3r]

It's how chocolatey works. The first path is a shim exe that forwards to the second. Akin to a symlink. That's why the go version command was saying it wasn't a go executable. Cause it's a shim.

[ldez]

So, installing golangci-lint with Chocolatey doesn't work with vscode, it's not a golangci-lint problem but a vscode-go extension problem.

FYI, the golangci-lint team is not part of the vscode-go team.
The Go organization maintains the extension.

I have an idea to "fix" the problem, but I'm not sure this will be accepted.

As a workaround, you install golangci-lint via the extension by using "go.lintTool": "golangci-lint-v2",

[adamk33n3r]

Ok, I made a comment on the linked issue in vscode-go. I will try this workaround thank you.

[adamk33n3r]

Seems like it's working now, though while using the recommended --fast-only flag I get no errors (while without it I get a ton) so this almost seems useless?

[ldez]

--fast-only filter linters to only keep "fast" linters, but if you want, you can remove it.