fix: do not use gaxServerStreamingRetries for bidi or client streaming #1575
Conversation
This file contains 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
leahecole
force-pushed
the
retries-template
branch
from
54dc88d
to
76d6c54
Compare
sofisl
approved these changes
Apr 16, 2024
leahecole
changed the title
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.
In preparation for selectively opting client libraries into the change, this PR adds some more fine grained changes for gax server streaming retries:
I have tested this successfully on nodejs-bigquery-storage and am testing it now with a new regeneration of the showcase test application as part of googleapis/gax-nodejs#1587