Skip to content

tools: tools version check logic is broken with go 1.18 #1939

Closed
@hyangah

Description

@hyangah

As reported in golang/go#50085 go 1.18 changes the encoding of the build info.
That means, if a tool is compiled with go1.18 and VS Code is configured to work with different versions of Go, go version -m command will fail.

The extension currently relies on go version -m for two things

We thought about utilizing go version -m to improve our tool update logic, but now I am afraid that this is an evidence that we shouldn't rely on go version -m unless the go version is the latest.

Currently the extension does not have logic to install the latest go version, or allow users to use different toolchains for tool management (probably we should. #825).

Metadata

Metadata

Assignees

Labels

FrozenDueToAgeNeedsFixThe path to resolution is known, but the work has not been done.release-blockermust be fixed before the next release.

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions