#10397 remoting: reintroduce retry limits to RE client Issue created by tdyas In switching to the "streaming" RE client, I removed the request retry logic in favor of relying on a deadline timeout. In validating the Pants client against Toolchain's build cluster, I noticed that certain misconfigurations on the server were reported to the client as retryable errors (e.g., the gRPC

UNAVAILABLE

status). Pants would see lots of these in a short space of time, but now does not report the issue or give up before the deadline timeout. From a user ergonomic perspective, Pants should short-circuit the deadline timeout if it hits a run of otherwise retryable errors since they may not in fact be retryable, and the user should get that feedback. cc @witty-crayon-22786 @illicitonion pantsbuild/pants

#10397 remoting: reintroduce retry limits to RE client Issue closed as not planned by tdyas pantsbuild/pants