Repository navigation
Bigtable: fix handling of unset rpc timeouts - #4323
Merged
igorbernstein2 merged 1 commit intoJan 11, 2019
Merged
Conversation
When the rpc timeout is zero, then it should be treated as disabled not actual 0
igorbernstein2
added
type: bug
googlebot
added
the
cla: yes
igorbernstein2
added
the
kokoro:force-run
yoshi-kokoro
removed
the
kokoro:force-run
sduskis
approved these changes
Jan 11, 2019
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
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.
When the rpc timeout is zero, then it should be treated as disabled not actual 0
Also, remove checks for null call context during call time, it can never be null after googleapis/gax-java#600.
And improve construction time null checks