fix(bigquery/storage/managedwriter): faster context failure on send #10169
+5
−0
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
This is a minor PR that accelerates the failure loop for context expiration cases. Previously, the connection abstraction would deal with expired context on the receiver side, and this change simply checks context before allowing a new append to succeed. Tests already existed that exhibited this behavior, but were timing dependent and masked the issue (the receiver would close the connection fast enough). Fixes: googleapis#10128
product-auto-label
bot
added
the
api: bigquery
alvarowolfx
approved these changes
May 14, 2024
shollyman
added
the
automerge
gcf-merge-on-green
bot
removed
the
automerge
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.
This is a minor PR that accelerates the failure loop for context expiration cases. Previously, the connection abstraction would deal with expired context on the receiver side, and this change simply checks context before allowing a new append to succeed.
Tests already existed that exhibited this behavior, but were timing dependent and masked the issue (the receiver would close the connection fast enough).
Fixes: #10128