Skip to content
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

Downloader: Treat 502 as recoverable HTTP error. #23378

Closed

Conversation

criemen
Copy link
Contributor

@criemen criemen commented Aug 21, 2024

GitHub releases sometimes fails with a 502 Bad Gateway error, as an internal request times out.
We want to retry these requests, so treat the 502 errors as the other 500s.

Fixes #23334

GitHub releases sometimes fails with a 502 Bad Gateway error,
as an internal request times out.
We want to retry these requests, so treat the 502 errors as
the other 500s.
@criemen criemen marked this pull request as ready for review August 21, 2024 11:36
@github-actions github-actions bot added team-ExternalDeps External dependency handling, remote repositiories, WORKSPACE file. awaiting-review PR is awaiting review from an assigned reviewer labels Aug 21, 2024
@criemen
Copy link
Contributor Author

criemen commented Aug 21, 2024

@meteorcloudy can you have a look at this PR?

@criemen
Copy link
Contributor Author

criemen commented Aug 21, 2024

@bazel-io fork 7.4.0

@meteorcloudy meteorcloudy added awaiting-PR-merge PR has been approved by a reviewer and is ready to be merge internally and removed awaiting-review PR is awaiting review from an assigned reviewer labels Aug 21, 2024
@meteorcloudy
Copy link
Member

@bazel-io fork 7.4.0

@github-actions github-actions bot removed the awaiting-PR-merge PR has been approved by a reviewer and is ready to be merge internally label Aug 22, 2024
bazel-io pushed a commit to bazel-io/bazel that referenced this pull request Aug 22, 2024
GitHub releases sometimes fails with a 502 Bad Gateway error, as an internal request times out.
We want to retry these requests, so treat the 502 errors as the other 500s.

Fixes bazelbuild#23334

Closes bazelbuild#23378.

PiperOrigin-RevId: 666244539
Change-Id: I2ed02ed9ecb3a7378c4d29b5ec5b96358e289779
github-merge-queue bot pushed a commit that referenced this pull request Aug 22, 2024
GitHub releases sometimes fails with a 502 Bad Gateway error, as an
internal request times out.
We want to retry these requests, so treat the 502 errors as the other
500s.

Fixes #23334

Closes #23378.

PiperOrigin-RevId: 666244539
Change-Id: I2ed02ed9ecb3a7378c4d29b5ec5b96358e289779

Commit
5081ddb

Co-authored-by: Cornelius Riemenschneider <cornelius@github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team-ExternalDeps External dependency handling, remote repositiories, WORKSPACE file.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bazel considers 502 Bad Gateway HTTP responses as unrecoverable
2 participants