[9.2.0] Remove the client gRPC message size limit (https://github.com/bazelbu…#29885
Merged
Merged
Conversation
Actions can have large `ActionResult`s due to their number of output files. Since the remote server is trusted anyway and the max message size is not a sizing hint, there is no point in limiting it. Fixes bazelbuild#29821 No - [x] I have added tests for the new use cases (if any). - [ ] I have updated the documentation (if applicable). RELNOTES: Bazel no longer limits the size of gRPC messages received from the remote executor or cache. Closes bazelbuild#29823. PiperOrigin-RevId: 933723049 Change-Id: I97ca2177fc6e8c3edc179257449e7892a7932929
coeuvre
approved these changes
Jun 19, 2026
Merged
via the queue into
bazelbuild:release-9.2.0
with commit Jun 19, 2026
5e8ea50
46 checks passed
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.
…ild/bazel/pull/29823)
Actions can have large
ActionResults due to their number of output files. Since the remote server is trusted anyway and the max message size is not a sizing hint, there is no point in limiting it.Fixes #29821
No
RELNOTES: Bazel no longer limits the size of gRPC messages received from the remote executor or cache.
Closes #29823.
PiperOrigin-RevId: 933723049
Change-Id: I97ca2177fc6e8c3edc179257449e7892a7932929
Description
Motivation
Build API Changes
No
Checklist
Release Notes
RELNOTES: None
Commit 5b92d9b