-
Notifications
You must be signed in to change notification settings - Fork 17.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cmd/go: improve "toolchain not available" message when patch version is missing #66175
Comments
CC @bcmills and @matloob via https://dev.golang.org/owners |
(CC @samthanawalla) |
it's worse in the case of no explicit TOOLCHAIN (if you set a toolchain I think it's reasonable that it'd be fully qualified) but completely baffling when happening indirectly through a See details in #62278 (comment) |
There are several approaches to work.
The Go Version, like Specifying language version in go directive without toolchain directive will make developers which need to download newer toolchain fail. I hope go command or any document notes that. |
Change https://go.dev/cl/580217 mentions this issue: |
Change https://go.dev/cl/583797 mentions this issue: |
Change https://go.dev/cl/583915 mentions this issue: |
…toolchain upgrade. This CL modifies the download behavior when downloading a toolchain for 1.21+. Previously, Go would attempt to download 1.X when upgrading the toolchain which would cause the download to fail for 1.21+ since 1.X is an invalid toolchain. We will attempt to download 1.X.0 since that's likely what the user intended. Additionally, we will also now provide a better error message when the user provides a language version instead of a toolchain version for 1.21+. For #66175 For #62278 Fixes #67236 Change-Id: I28f894290a19d8e3cd220e9d70aeca8f4447e5a1 Reviewed-on: https://go-review.googlesource.com/c/go/+/580217 Reviewed-by: Michael Matloob <[email protected]> LUCI-TryBot-Result: Go LUCI <[email protected]> (cherry picked from commit 27ed85d) Reviewed-on: https://go-review.googlesource.com/c/go/+/583915
…toolchain upgrade. This CL modifies the download behavior when downloading a toolchain for 1.21+. Previously, Go would attempt to download 1.X when upgrading the toolchain which would cause the download to fail for 1.21+ since 1.X is an invalid toolchain. We will attempt to download 1.X.0 since that's likely what the user intended. Additionally, we will also now provide a better error message when the user provides a language version instead of a toolchain version for 1.21+. For #66175 For #62278 Fixes #67235 Change-Id: I28f894290a19d8e3cd220e9d70aeca8f4447e5a1 Reviewed-on: https://go-review.googlesource.com/c/go/+/580217 Reviewed-by: Michael Matloob <[email protected]> LUCI-TryBot-Result: Go LUCI <[email protected]> (cherry picked from commit 27ed85d) Reviewed-on: https://go-review.googlesource.com/c/go/+/583797
* get pods from context default config * I hate that horrible toolchain thing... golang/go#66175 (comment) * improve output a bit and explain that empty == all namespaces * Add comment for where clientcmd.NewNonInteractiveDeferredLoadingClientConfig is coming from * simpler version, that also gets 'default' instead of '' * add flags to override --context, --namespace etc
Seems like the latest Go require the minor version to be explicitly defined [1][2]. [1] golang/go#65568 [2] golang/go#66175
See also golang/go#66175 Otherwise can't build: go: download go1.22 for linux/amd64: toolchain not available Signed-off-by: Oleg Vasilev <[email protected]>
See also golang/go#66175 Otherwise can't build: go: download go1.22 for linux/amd64: toolchain not available Signed-off-by: Oleg Vasilev <[email protected]>
See also golang/go#66175 Otherwise can't build: go: download go1.22 for linux/amd64: toolchain not available Signed-off-by: Oleg Vasilev <[email protected]>
Change https://go.dev/cl/621861 mentions this issue: |
This avoids distracting users who are still using go without the fix for golang/go#66175. Change-Id: I8847cc54632c72ef334cfc63d8d560644d9ececc Reviewed-on: https://go-review.googlesource.com/c/oscar/+/621861 Reviewed-by: Jonathan Amsterdam <[email protected]> LUCI-TryBot-Result: Go LUCI <[email protected]>
It took me a long while to figure out that the cause of the problem was a missing patch version suffix (
.0
). Either the go command should pick a reasonable suffix itself, or it should report that I am expected to provide one.The text was updated successfully, but these errors were encountered: