4

proxy.golang.org: widespread not found: fetch timed out · Issue #57185 · golang/...

 1 year ago
source link: https://github.com/golang/go/issues/57185
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
neoserver,ios ssh client

Comments

I pushed an untagged commit to the github.com/scjalliance/astconf module 3 hours ago, but sum.golang.org claims that it can't find it when requesting its pseudo-version v0.0.0-20221209034541-5c12b5578696. It returns a 404 Not Found result.

Running go list -m for the branch does list the expected commit, but takes a very long time to run:

time go list -m -json github.com/scjalliance/astconf@main
{
        "Path": "github.com/scjalliance/astconf",
        "Version": "v0.0.0-20221209034541-5c12b5578696",
        "Query": "main",
        "Time": "2022-12-09T03:45:41Z",
        "Origin": {
                "VCS": "git",
                "URL": "https://github.com/scjalliance/astconf",
                "TagSum": "t1:47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=",
                "Ref": "refs/heads/main",
                "Hash": "5c12b5578696a1517acd34d3c60d88b303b0b964"
        }
}

real    2m55.660s
user    0m0.115s
sys     0m0.068s

Performing a go get for the branch returns server response: not found: fetch timed out:

go get github.com/scjalliance/astconf@main
go: downloading github.com/scjalliance/astconf v0.0.0-20221209034541-5c12b5578696
go: github.com/scjalliance/astconf@main: github.com/scjalliance/[email protected]: verifying module: github.com/scjalliance/[email protected]: reading https://sum.golang.org/lookup/github.com/scjalliance/[email protected]: 404 Not Found
        server response: not found: fetch timed out

I get a not found: fetch timed out response after waiting 58 seconds when I go here:

I don't know if it matters, but I did perform a forced git push to the astconf repository earlier in the evening, and I renamed the branch from master to main yesterday.

I should also note that pkg.go.dev lists v0.0.0-20221209023833-cad60e1e1338 as the latest version right now, but when viewing that version specifically it also claims that it isn't the latest version. I used the package request feature of pkg.go.dev to request the v0.0.0-20221209023833-cad60e1e1338 release earlier this evening.

I've been watching the GitHub Status Page and it claims all is well.

I am filing this report as directed by the FAQ on sum.golang.org, which was added in response to #42809:

Note that if someone requested the version before the tag was pushed, it may take up to 30 minutes for the mirror's cache to expire and fresh data about the version to become available. If the version is still not available after 30 minutes, please file an issue.

I first encountered this issue while running the Go 1.19.2 tooling on windows/amd64. I updated to 1.19.4 but the issue persists. The slow response to go list -m was reproduced in a linux environment.

clementnuss, LeGEC, vvakame, buzztaiki, IvanZenger, emmaly, ludwig-nyberg, general-kroll-4-life, niamster, radhus, and 65 more reacted with thumbs up emoji

About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK