We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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 version
I'm using a build server (Google Cloud Build) and golang:1.12.7-buster
golang:1.12.7-buster
Yes, confident that it's proxy related
For the purposes of testing, artificially constrained: go.mod:
module ${MODULE} go 1.12 require ( github.com/google/trillian v1.3.0 )
Successful build; this happens if I set the build's GOPROXY=direct
GOPROXY=direct
Failed build; this happens if I set the build's GOPROXY=https://proxy.golang.org and
GOPROXY=https://proxy.golang.org
google.golang.org/[email protected]: unexpected status (https://proxy.golang.org/google.golang.org/genproto/@v/v0.0.0-20170818100345-ee236bd376b0.info): 410 Gone mvdan.cc/[email protected]: unexpected status (https://proxy.golang.org/mvdan.cc/unparam/@v/v0.0.0-20190124213536-fbb59629db34.info): 410 Gone github.com/golangci/[email protected]: unexpected status (https://proxy.golang.org/github.com/golangci/ineffassign/@v/v0.0.0-20180808204949-42439a7714cc.info): 410 Gone github.com/golangci/[email protected]: unexpected status (https://proxy.golang.org/github.com/golangci/gosec/@v/v0.0.0-20180901114220-66fb7fc33547.info): 410 Gone github.com/golangci/[email protected]: unexpected status (https://proxy.golang.org/github.com/golangci/go-tools/@v/v0.0.0-20180109140146-af6baa5dc196.info): 410 Gone github.com/golangci/[email protected]: unexpected status (https://proxy.golang.org/github.com/golangci/errcheck/@v/v0.0.0-20181003203344-ef45e06d44b6.info): 410 Gone github.com/golangci/[email protected]: unexpected status (https://proxy.golang.org/github.com/golangci/lint-1/@v/v0.0.0-20180610141402-ee948d087217.info): 410 Gone github.com/go-critic/[email protected]: unexpected status (https://proxy.golang.org/github.com/go-critic/go-critic/@v/v0.0.0-20181204210945-1df300866540.info): 410 Gone github.com/russross/blackfriday/[email protected]+incompatible: unexpected status (https://proxy.golang.org/github.com/russross/blackfriday/v2/@v/v2.0.1+incompatible.info): 410 Gone github.com/golangci/[email protected]: unexpected status (https://proxy.golang.org/github.com/golangci/gofmt/@v/v0.0.0-20181105071733-0b8337e80d98.info): 410 Gone
Which appear to (all) be:
invalid pseudo-version: does not match version-control timestamp
This may indeed be accurate but my solution is to avoid using the proxy :-(
The text was updated successfully, but these errors were encountered:
See https://tip.golang.org/doc/go1.13#version-validation for workarounds.
Sorry, something went wrong.
Duplicate of #32805
No branches or pull requests
What version of Go are you using (
go version
)?I'm using a build server (Google Cloud Build) and
golang:1.12.7-buster
Does this issue reproduce with the latest release?
Yes, confident that it's proxy related
What did you do?
For the purposes of testing, artificially constrained:
go.mod:
What did you expect to see?
Successful build; this happens if I set the build's
GOPROXY=direct
What did you see instead?
Failed build; this happens if I set the build's
GOPROXY=https://proxy.golang.org
andWhich appear to (all) be:
This may indeed be accurate but my solution is to avoid using the proxy :-(
The text was updated successfully, but these errors were encountered: