-
Notifications
You must be signed in to change notification settings - Fork 17.5k
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
verifying module@v0.9.0/go.mod: ... reading module@v0.9.0: 410 Gone #36183
Comments
If this is a new tag, almost certainly duplicate of #34370 (comment). |
For posterity, the error from the sumdb: |
The tag was posted several minutes before the command though? |
I don't think this is a duplicate, because in that issue the tag was created after the command was run, but for me, the tag was created before running the command. Edit: Well, it's working now. But it sure would be nice if the repo owner could tell the cache to invalidate a wrong state. |
Your first command was run at |
That is weird, though. Doesn't match up with what I did, I wonder if there was some lag in a system between my computer and the proxy and the git server. |
And the cache has just expired: aofei@as-macbook-pro:~$ curl -i https://sum.golang.org/lookup/github.com/mholt/certmagic@v0.9.0
HTTP/2 200
accept-ranges: bytes
content-length: 365
content-type: text/plain; charset=UTF-8
date: Tue, 17 Dec 2019 17:54:02 GMT
expires: Tue, 17 Dec 2019 20:54:02 GMT
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
x-xss-protection: 0
cache-control: public, max-age=10800
age: 118
546235
github.com/mholt/certmagic v0.9.0 h1:dYh9sZPDBTcIiPhYM/Qtv3V623/zFH34FmpbrQTpMAc=
github.com/mholt/certmagic v0.9.0/go.mod h1:91uJzK5K8IWtYQqTi5R2tsxV1pCde+wdGfaRaOZi6aQ=
go.sum database tree
546279
uVHuaN+c8KtdVSSph74Y+Zmdma8fYIqx7HMDhFjoaok=
— sum.golang.org Az3groND3X+FPNnslWNpFahhwLVCH4Ww5b0OEi5KpyPEWplyvt4qc00TB/pcpRgDKzJQQql7DnNiTWcKAHnPijt3ego= |
I checked the internal logs for proxy/sum.golang.org. The first request they ever got for certmagic v0.9.0 was at 2019-12-17 17:23:35 UTC, which is the request that resulted in the negative cache entry in question. The GitHub UI for https://github.com/mholt/certmagic/releases/tag/v0.9.0 says that it was tagged at 12:22 EST, or 17:22 UTC. I don't have any explanation for the mismatch; the go command just says that it couldn't find that version. Was the tag created using the GitHub UI, in which case maybe there's some delay there? |
No, it was command line. Maybe it took GitHub a minute to sync or something. Thanks for looking into it. |
Incidentally, 410 Gone means:
This is clearly not the case with the module cache. Additionally, perhaps negative hits should not be cached. |
410 is necessary for internal implementation reasons. The need for negative caching is described in #34370 (comment). |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Run:
What did you expect to see?
No error
What did you see instead?
This is weird, because the tag is new and unmodified (no deletions, no renames, no force pushes, etc) -- I am the only one who has committed to this repo at all recently (like, in the last several weeks/months) and I need to use the v0.9.0 tag for a new build: https://github.com/mholt/certmagic/tree/v0.9.0
Edit:
Also tried
GOPROXY=direct
and the same error.(The tag is "new" but several minutes old.)
The text was updated successfully, but these errors were encountered: