Fix GRPC Retry Configuration #916
Merged
Conversation
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
jribbink
requested review from
chasefleming,
janezpodhostnik,
mfbz and
peterargue
as code owners
jribbink
force-pushed
the
jribbink/bump-rate-limit
branch
from
9caddcf to
ba67ec4
Compare
jribbink
changed the title
jribbink
commented
Nov 18, 2025
chasefleming
approved these changes
Nov 18, 2025
jribbink
force-pushed
the
jribbink/bump-rate-limit
branch
from
aea1327 to
ebe7780
Compare
Contributor
Author
|
See #917 |
6 tasks
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.
Fix GRPC retry configuration to include explicit service matchers & adjust retry parameters. This was previously causing flaky CI as the wildcard matcher did not work as intended.