top | item 33920318 proxy.golang.org issues affecting 'go get' 5 points| mariusor | 3 years ago |github.com | reply 3 comments order hn newest [+] [-] capableweb|3 years ago|reply Isn't the entire point behind using URIs as "modules URIs" that it's decentralized so the load is spread across hosts and there isn't a single point of failure? Is Golang proxying all those fetches regardless? [+] [-] galenguyer|3 years ago|reply It is: https://proxy.golang.org/. The goal is faster module downloads, and to an extent prevent users from hitting GitHub/etc ratelimits [+] [-] mariusor|3 years ago|reply A temporary solution to the issue is to remove proxying for packages download:go env -w GOPROXY=directgo env -w GOSUMDB=off
[+] [-] capableweb|3 years ago|reply Isn't the entire point behind using URIs as "modules URIs" that it's decentralized so the load is spread across hosts and there isn't a single point of failure? Is Golang proxying all those fetches regardless? [+] [-] galenguyer|3 years ago|reply It is: https://proxy.golang.org/. The goal is faster module downloads, and to an extent prevent users from hitting GitHub/etc ratelimits
[+] [-] galenguyer|3 years ago|reply It is: https://proxy.golang.org/. The goal is faster module downloads, and to an extent prevent users from hitting GitHub/etc ratelimits
[+] [-] mariusor|3 years ago|reply A temporary solution to the issue is to remove proxying for packages download:go env -w GOPROXY=directgo env -w GOSUMDB=off
[+] [-] capableweb|3 years ago|reply
[+] [-] galenguyer|3 years ago|reply
[+] [-] mariusor|3 years ago|reply
go env -w GOPROXY=direct
go env -w GOSUMDB=off