-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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
x/exp: depends on unreliable repository #35221
Comments
a) x/exp is experimental. b) if you're using proxy.golang.org or another module proxy/cache, then it doesn't matter whether something is up or not. /cc @dmitshur |
Im acutally not using x/exp directly - go mod graph shows that it is used by cloud.google.com/[email protected] Perhaps they should not be using x/exp. |
Thank @bradfitz - setting Thanks again for your help! |
It's fixed now, this was https://twitter.com/dmitshur/status/1188949522724073472. I would've made the same suggestion as @bradfitz to use https://proxy.golang.org. Glad it worked well for you. |
@dmitshur Looks like the server https://dmitri.shuralyov.com/gpu/mtl failed again to day. Could you help check?
Setting |
Does the Go team has any plan or checklist or document on using non reliable source (for both release and experimental packages)? If yes then could you help direct me to it? I need it for our company's incident report since this issue block our CI/CD pipeline. Thanks a lot. |
Can anyone advise how to set GOPROXY when deploying to Google AppEngine Standard? |
me too. I'm using AppEngine 1st gen still, It uses Go 1.11 ... We wanna move into 2nd gen. But it's not easy for our teams. |
Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only. For asking questions, see:
|
Thank you @davecheney! |
Our current CI builds are failing because https://dmitri.shuralyov.com/gpu/mtl is not online enough. Investigating this I can see that x/exp depends on it.
Is it possible to only add reliable dependencies to the core golang library? This causes a lot of lost time due to CI breakage and folk having to investigate this.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
It is intermittent - CI builds break with
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
What did you expect to see?
CI builds succeeding
What did you see instead?
Flakey breakage
The text was updated successfully, but these errors were encountered: