-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
go get cmd/golangci-lint fails on Go 1.13 (tip) which uses proxy.golang.org (HTTP error 410 Gone) #595
Comments
Related to this issue, on our CI builds we've started to notice 400 HTTP error (Bad Request) reported by ref: https://travis-ci.org/llir/llvm/jobs/552889788
Edit: It seems like other dependencies of
|
It also seems that on Go 1.13 (tip), it is not possible to
|
This is used to mitigate CI failure when go get fails for golangci-lint (ref golangci/golangci-lint#595)
Re-enable golangci-lint once golangci/golangci-lint#595 is resolved.
I've submitted a PR that fixes the issue |
I have similar issue too:
|
Pretty sure this is the same issue, but our circleci broke earlier this week, with errors such as:
Digging into the server response, the actual underlying problem is that the pseudo version doesn't match due to the timestamp being different. Going directly to
From what I understand, go1.13 is stricter than go1.12 about timestamps matching, and the proxy has adopted the same behavior. I was able to work around these build problems using a series of replace statements in
|
Im able to resolve the issue by setting |
@dustmop thanks for that 🙃 for v1.17.1 I had to tweak to:
for master I had to add:
|
Hmm. I wish I had found this about 10 minutes ago. ;-) FWIW, using Go 1.13, these steps fail with an "invalid pseudo-version" error:
which reports error:
If we follow the advice from the section of the Go 1.13 release notes on resolving version validation issues (https://golang.org/doc/go1.13#version-validation), we can make that same 'go get' work:
This now works:
|
Hi, sorry for slow fixing. |
go version && go env
go version
output:go env
output:On the latest version of Go (which uses
proxy.golang.org
) it seems likego get
is resulting in a 410 HTTP error.The text was updated successfully, but these errors were encountered: