-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
proxy.golang.org: long cache TTL causes confusing UX for 'go get <module>@<branchname>' #38065
Comments
The code is in gitgub.com/RainwayApp/MetaPod/src/metapod |
This comment has been minimized.
This comment has been minimized.
Note that commit |
(I'm trying to find the right issue to mark this as a duplicate.) |
I sort of expected that to be the case - just didnt know where in the chain that happened. Is there any reason why the commit hash in the error message is different to the one in the module cache path ( |
Yeah and the error message that i copied in i think is wrong it should be for |
Perhaps pkg.go.dev could have a "check for newer version" button. The TTL could be communicated by greying that button out with a "try again in X minutes" message. |
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?
go get github.com/RainwayApp/metapod@modulize
and then attempt to import and use metapod in a programWhat did you expect to see?
No errors! woo!
What did you see instead?
module github.com/RainwayApp/metapod@latest found (v0.0.0-20190515153323-337878358c65), but does not contain package github.com/RainwayApp/metapod
Whats interesting is that the downloaded module is devoid of go files which I dont really get (this is even after trying to go get the module again after deleting it from here).

I got around this by creating a new branch (modulize2) which has all the files - however im not sure how its possible for it to end up in this state in the first place so just thought id bring it up...
The text was updated successfully, but these errors were encountered: