-
Notifications
You must be signed in to change notification settings - Fork 62
tests: System/compatibility tests for testing shim compatiblity #1218
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
gkevinzheng
wants to merge
13
commits into
v3_staging
Choose a base branch
from
system-tests-legacy
base: v3_staging
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+834
−4
Open
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
807ae39
tests: System/compatibility tests for testing shim compatiblity
gkevinzheng e86899a
🦉 Updates from OwlBot post-processor
gcf-owl-bot[bot] 0426ce2
Use 3.12 instead of 3.8 for system tests
gkevinzheng cca6ccd
linting
gkevinzheng 1bd0230
🦉 Updates from OwlBot post-processor
gcf-owl-bot[bot] b3ce1cd
Skipped sample_row_keys test on emulator
gkevinzheng e06550e
Merge branch 'v3_staging' into system-tests-legacy
gkevinzheng 4499e4b
Use 3.12 instead of 3.8 for system tests
gkevinzheng a895bc2
Addressed review feedback
gkevinzheng a16360c
Update test_data_api.py
gkevinzheng 533dba1
Delete test.out
gkevinzheng 68a91be
Delete .kokoro/presubmit/system-3.12.cfg
gkevinzheng 72cc5bb
Delete bigtable_delete.sh
gkevinzheng File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why was this change needed?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change was needed because the
read_rows
method that gets passed in gets called with the GAPIC default retry instead of the retry that the user passed in orDEFAULT_READ_RETRY
for this instance. If there's an error with this specific instance ofself.read_method
it doesn't get retried and errors out.For example, if a retriable
InternalError
occurred mid-stream, then in thison_error
handler the same error occurred, the error in theon_error
handler would not be retried because the specific retry was not passed in for that RPC call.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a bit torn, because this does feel like a very real bug. But the code here is also very complex, so I'm hesitant to make changes to the retry policy in case there are side-effects we're not considering
But I guess this is coming in the context of adding more system tests. Do you think the tests we have now are sufficient to catch any errors?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, on second thought, this is a PR into the v3_staging branch, not main. We will be doing much more extensive changes here as part of the shim, before cutting a release. So I think adding this fix makes sense