Description of the feature request:
We recently started failing BES upload to BuildBuddy as we passed their 50 MB default GRPC message limit: https://github.com/buildbuddy-io/buildbuddy/blob/master/server/util/grpc_server/grpc_server.go#L42
On this particular message. I worked around it by increasing that configuration to 200 MB, but overall it would be better if this message didnt scale so huge.
The issue is the TargetConfigured id for every target. We have a ton of targets in a large monorepo. Can we stop stuffing all this into one event and instead announce them in batched Progress events (same idea as --build_event_max_named_set_of_file_entries)?
Which category does this issue belong to?
No response
What underlying problem are you trying to solve with this feature?
Large GRPC messages hitting server side reasonable limits
Which operating system are you running Bazel on?
CentOS 9 Stream
What is the output of bazel info release?
release 9.2.0
If bazel info release returns development version or (@non-git), tell us how you built Bazel.
No response
What's the output of git remote get-url origin; git rev-parse HEAD ?
Have you found anything relevant by searching the web?
Similar #12050
Any other information, logs, or outputs that you want to share?
No response
Description of the feature request:
We recently started failing BES upload to BuildBuddy as we passed their 50 MB default GRPC message limit: https://github.com/buildbuddy-io/buildbuddy/blob/master/server/util/grpc_server/grpc_server.go#L42
On this particular message. I worked around it by increasing that configuration to 200 MB, but overall it would be better if this message didnt scale so huge.
The issue is the
TargetConfiguredid for every target. We have a ton of targets in a large monorepo. Can we stop stuffing all this into one event and instead announce them in batchedProgressevents (same idea as --build_event_max_named_set_of_file_entries)?Which category does this issue belong to?
No response
What underlying problem are you trying to solve with this feature?
Large GRPC messages hitting server side reasonable limits
Which operating system are you running Bazel on?
CentOS 9 Stream
What is the output of
bazel info release?release 9.2.0
If
bazel info releasereturnsdevelopment versionor(@non-git), tell us how you built Bazel.No response
What's the output of
git remote get-url origin; git rev-parse HEAD?Have you found anything relevant by searching the web?
Similar #12050
Any other information, logs, or outputs that you want to share?
No response