You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Go Report Card for my repository github.com/cyclone-github/hashgen is nearly 2 years out of date and does not reflect the current state of the repository. Upon investigating, it appears that Go Report Card is using an incorrect URL when attempting to fetch / refresh the latest module version which results in an error.
Error when Refreshing Go Report Card:
There was an error processing your request: Could not analyze the repository: could not download repo: could not get latest module version from https://proxy.golang.org/hashgen/@latest
Testing output from currently used URL: https://proxy.golang.org/hashgen/@latest
bad request: invalid escaped module path "hashgen": malformed module path "hashgen": missing dot in first path element
Testing output from corrected URL: https://proxy.golang.org/github.com/cyclone-github/hashgen/@latest
This issue is due to Go Report Card using an incorrect URL to fetch / refresh GitHub repositories. This only seems to affect older repositories as new repositories use the correct URL in my testing. https://proxy.golang.org/{username}/{repo}/@latest
Fix:
Force Fetch / Refresh to use the correct URL: https://proxy.golang.org/github.com/{username}/{repo}/@latest
The text was updated successfully, but these errors were encountered:
The Go Report Card for my repository
github.com/cyclone-github/hashgen
is nearly 2 years out of date and does not reflect the current state of the repository. Upon investigating, it appears thatGo Report Card
is using an incorrect URL when attempting to fetch / refresh the latest module version which results in an error.Error when Refreshing Go Report Card:
Testing output from currently used URL:
https://proxy.golang.org/hashgen/@latest
Testing output from corrected URL:
https://proxy.golang.org/github.com/cyclone-github/hashgen/@latest
Issue:
This issue is due to
Go Report Card
using an incorrect URL to fetch / refresh GitHub repositories. This only seems to affect older repositories as new repositories use the correct URL in my testing.https://proxy.golang.org/{username}/{repo}/@latest
Fix:
Force
Fetch
/Refresh
to use the correct URL:https://proxy.golang.org/github.com/{username}/{repo}/@latest
The text was updated successfully, but these errors were encountered: