fix(cli): remove ResourceExhausted from retriable gRPC codes#3054
Merged
migmartri merged 1 commit intoApr 17, 2026
Merged
Conversation
ResourceExhausted typically signals rate limiting or quota exhaustion. Blanket-retrying it can waste work against hard quotas and amplify load on an overloaded server. gRPC guidance is to only retry when the server explicitly signals safety via RetryInfo metadata. Refs chainloop-dev#3053 Signed-off-by: Miguel Martinez Trivino <miguel@chainloop.dev>
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
jiparis
approved these changes
Apr 17, 2026
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
2 participants
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.
Summary
Removes
codes.ResourceExhaustedfrom the CLI's set of retriable gRPC error codes inapp/cli/cmd/errors.go.ResourceExhaustedtypically signals rate limiting or quota exhaustion. Blanket-retrying it can waste work against hard quotas that will not self-recover within the retry window, and can amplify load on an already overloaded server. Standard gRPC guidance is to only retryResourceExhaustedwhen the server explicitly signals it is safe viaRetryInfometadata.Retries remain for
Unavailable,Internal, andDeadlineExceeded.Closes #3053