Amir Omidi

I've now added ``` common '--repo_env=GOPROXY=https://goproxy.io,https://proxy.golang.org,direct' ``` To my bazelrc, which effectively just changes GOPROXY. So far it seems we've not hit these errors. I'll keep an eye out on...

I have not seen this issue happen since we’ve changed GOPROXY. I’ll still keep an eye out on it.

I've switched us over to the following `bazelrc` incantation: ``` common '--repo_env=GOPROXY=https://proxy.golang.org|https://goproxy.io|direct' ```

I've for now switched to using multiple proxies, so I dont think I'll be able to know for certain..

I just ran into this locally again when using only proxy.golang.org. ``` loading failure: com.google.devtools.build.lib.rules.repository.RepositoryFunction$AlreadyReportedRepositoryAccessException: gazelle~~go_deps~com_github_aws_aws_sdk_go_v2_service_internal_presigned_url: fetch_repo: github.com/aws/aws-sdk-go -v2/service/internal/[email protected]: Get "https://proxy.golang.org/github.com/aws/aws-sdk-go-v2/service/internal/presigned-url/@v/v1.12.2.info": dial tcp 142.250.81.241:443: i/o timeout ```

If I retry it does succeed. I don't see it _that often_, but that's partially because of heavy caching on my end. I no longer see this in CI after...

This has nothing to do with AWS for what it’s worth. I’ve had this issue on GitHub actions which would be azure. I don’t think it’s the network either. This...

I’m not sure that’s true though. Especially given Bazel and go are both Google projects. I think realistically this is only really actionable by Google by involving the Bazel team...

@Lagoja I'm currently in the process of talking to a few folks about writing something for this. I'll probably use the same license as what devbox uses, so we can...

A proof of concept is now available here: https://github.com/aaomidi/rules_devbox. This only supports the most basic use case of devbox, where you're just relying on a package directly from nixpkgs. Future...