Don't reset the retry budget on each ByteStream response - #30820
Draft
fmeum wants to merge 1 commit into
Draft
Conversation
ByteStream `ReadResponse's should reset the timeout (as they do via `RemoteDownloadIdleTimeoutInterceptor`), but not the retry budget, otherwise failing reads can keep retrying indefinitely. Fixes bazelbuild#30780
Collaborator
Author
|
@bazel-io fork 9.3.0 |
|
✅ Bazel docs preview is ready! Preview URL: https://bazel-pr-30820.mintlify.app/ Updated for |
fmeum
marked this pull request as draft
August 20, 2026 16:09
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
ByteStream
ReadResponses should reset the timeout (as they do viaRemoteDownloadIdleTimeoutInterceptor), but not the retry budget, otherwise failing reads can keep retrying indefinitely.Motivation
Fixes #30780
Build API Changes
No
Checklist
Release Notes
RELNOTES: None