Dmytro Kashyn

``` ❯ cat .bazelrc | grep -e bes -e event #build --bes_backend=grpcs://... #build --bes_upload_mode=fully_async #build --build_event_text_file_upload_mode=fully_async #build --build_event_binary_file_upload_mode=fully_async #build --build_event_json_file_upload_mode=fully_async ``` I see [rbe_another_dump.txt](https://github.com/bazelbuild/bazel/files/14594580/rbe_another_dump.txt) This time RBE server might be...

[rbe_yet_another_dump.txt](https://github.com/bazelbuild/bazel/files/14602205/rbe_yet_another_dump.txt)

As you can see here https://github.com/bazelbuild/bazel/issues/21626#issuecomment-1994457946 we don't have this enabled. I still can turn it off if required though.

Ok... I see it is enabled by default. Let me turn that off ``` @Option( name = "experimental_throttle_remote_action_building", defaultValue = "true", ```

What to do with BES/BEP and `keep_alive` that were turned off earlier ?

This flag is 8.x only, based on https://github.com/bazelbuild/bazel/commit/294c904c30fe305f60e548a438940d5ab60a15b4 I got ``` ERROR: --noexperimental_throttle_remote_action_building :: Unrecognized option: --noexperimental_throttle_remote_action_building ``` for ``` cat .bazelversion 7.0.1 ``` So I'd say this is definitely...

It might take a couple of weeks for us to upgrade to 7.1 . We definitely going to do this in either case yet amount of features we currently disabled...

Ok, let us focus on testing this particular condition next week then.

We were able to use `7.1` and TO is still there I have another run stuck in ``` [65,743 / 65,759] ...; 3777s remote, disk-cache, remote-cache ``` with ``` #common:remote...

@coeuvre could you please take a look whether new stacktraces and info from @werkt is helpful with identifying the issue?