Skip to content

Don't reset the retry budget on each ByteStream response - #30820

Draft
fmeum wants to merge 1 commit into
bazelbuild:masterfrom
fmeum:fix-bytestream-download-retry-budget
Draft

Don't reset the retry budget on each ByteStream response#30820
fmeum wants to merge 1 commit into
bazelbuild:masterfrom
fmeum:fix-bytestream-download-retry-budget

Conversation

@fmeum

@fmeum fmeum commented Aug 20, 2026

Copy link
Copy Markdown
Collaborator

Description

ByteStream ReadResponses should reset the timeout (as they do via RemoteDownloadIdleTimeoutInterceptor), but not the retry budget, otherwise failing reads can keep retrying indefinitely.

Motivation

Fixes #30780

Build API Changes

No

Checklist

  • I have added tests for the new use cases (if any).
  • I have updated the documentation (if applicable).

Release Notes

RELNOTES: None

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
@fmeum
fmeum requested a review from a team as a code owner August 20, 2026 14:50
@github-actions github-actions Bot added team-Remote-Exec Issues and PRs for the Execution (Remote) team awaiting-review PR is awaiting review from an assigned reviewer labels Aug 20, 2026
@fmeum

fmeum commented Aug 20, 2026

Copy link
Copy Markdown
Collaborator Author

@bazel-io fork 9.3.0

@bazel-docs-pr-commenter

Copy link
Copy Markdown

✅ Bazel docs preview is ready!

Preview URL: https://bazel-pr-30820.mintlify.app/

Updated for 3c3ca0f19cdb91a89e5b4ce9baefccff5f0444db

@fmeum
fmeum marked this pull request as draft August 20, 2026 16:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

awaiting-review PR is awaiting review from an assigned reviewer team-Remote-Exec Issues and PRs for the Execution (Remote) team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bazel 9.2 hangs indefinitely after a remote-cache ByteStream read times out

1 participant