proxy.golang.org: dial tcp 142.251.33.113:443: i/o timeout

[jfirebaugh]

What version of Go are you using (go version)?

1.21.0

Does this issue reproduce with the latest release?

n/a

What operating system and processor architecture are you using (go env)?

go env Output

$ go env

What did you do?

Downloads from proxy.golang.org (via rules_go) are intermittently failing with networking timeouts.

What did you expect to see?

Successful package downloads.

What did you see instead?

ERROR: An error occurred during the fetch of repository 'com_github_aws_aws_sdk_go_v2_internal_configsources':
   Traceback (most recent call last):
	File "/home/circleci/.cache/bazel/_bazel_circleci/a6e8cb0ce75ceb1ea1faa0cca0b0ae0d/external/bazel_gazelle/internal/go_repository.bzl", line 254, column 17, in _go_repository_impl
		fail("failed to fetch %s: %s" % (ctx.name, result.stderr))
Error in fail: failed to fetch com_github_aws_aws_sdk_go_v2_internal_configsources: fetch_repo: github.com/aws/aws-sdk-go-v2/internal/[email protected]: Get "https://proxy.golang.org/github.com/aws/aws-sdk-go-v2/internal/configsources/@v/v1.1.34.info": dial tcp 142.251.33.113:443: i/o timeout

[seankhliao]

are you sure it's not a network problem local to you?

[bcmills]

@jfirebaugh, I think we would need more evidence before treating this as a problem with the proxy itself.

In the past we have seen connection timeouts on the Go CI builders due to port exhaustion (see #52545 (comment)). If your timeout is on the order of the TIME-WAIT delay on your host or shorter, you might consider that as a possible cause on that end.

[jfirebaugh]

Fair enough. The issue self-resolved at 9:00 PT.