extension crashes if go.mod uses language version and the local go version is older than the go version in go.mod

[hyangah]

Repro case:

$ GOTOOLCHAIN=local go version
go1.21.9
$ cat go.mod
module w

go 1.22

Failed to run '/usr/local/go/bin/go env' (cwd: /Users/hakim/projects/go-qrcode): Error: Command failed: /usr/local/go/bin/go env -json GOPATH GOROOT GOPROXY GOBIN GOMODCACHE
go: downloading go1.22 (darwin/amd64)
go: download go1.22 for darwin/amd64: toolchain not available

go: downloading go1.22 (darwin/amd64)
go: download go1.22 for darwin/amd64: toolchain not available

The root cause is
golang/go#65580
that was closed as a duplicate of golang/go#62278,
which was closed in favor of a better error message.

cc @golang/tools-team

[rhcarvalho]

I'm seeing a similar problem, but go.work instead of go.mod. I believe the underlying problem to be the same.

Error loading workspace: packages.Load error: err: exit status 1: stderr: go: go.work requires go >= 1.22.3 (running go 1.22.2)

Running go version on the integrated terminal gives:

go version go1.22.3 linux/amd64

Thus the go1.22.2 toolchain was able to download and use the go1.22.3 toolchain, but gopls doesn't pick it up.

[matloob]

@hyangah We expect this to be fixed once 1.21.11 is released with the backported change to download 1.22.0 when 1.22 is listed in go.mod, right?

[heppu]

Still running in to this issue:

Error loading workspace: packages.Load error: err: exit status 1: stderr: go: go.work requires go >= 1.24.1 (running go 1.23.6)

I don't understand where that go 1.23.6 version is coming from.

$ go version                
go version go1.24.1 linux/amd64

go.work

go 1.24.1

toolchain go1.24.1

[delca85]

@heppu which is the IDE you are working? I managed to fix this manually selecting the go version used by VSCode (even if the IDE was already showing Go 1.24.1 as used version).

[heppu]

I'm using vscode-insider. I think this is gopls issue. I can see that gopls is build with 1.23.6 toolchain:

## Tools
	go:	/usr/bin/go: go version go1.24.0 linux/amd64
	gopls:	/home/heppu/go/bin/gopls	(version: v0.18.1 built with go: go1.23.6)
	gotests:	/home/heppu/go/bin/gotests	(version: v1.6.0 built with go: go1.24.0)
	gomodifytags:	/home/heppu/go/bin/gomodifytags	(version: v1.17.0 built with go: go1.24.0)
	impl:	/home/heppu/go/bin/impl	(version: v1.4.0 built with go: go1.24.0)
	goplay:	/home/heppu/go/bin/goplay	(version: v1.0.0 built with go: go1.24.0)
	dlv:	/home/heppu/go/bin/dlv	(version: v1.24.1 built with go: go1.24.0)
	golangci-lint:	/home/heppu/go/bin/golangci-lint	(version: v1.64.6 built with go: go1.24.0)

[heppu]

Building gopls from master with go1.24.1 seemed to fix this issue.

EDIT: I was to quick, it didn't fix the issue.

[bweston92]

@heppu did you manage to find a fix?

[heppu]

@bweston92 Nope but I think there was a gopls ticket when I was googling about it.