Uh oh!
There was an error while loading. Please reload this page.
Revert "Add RPC retries to Bigtable (#3811)" - #4524
Merged
Merged
Conversation
igorbernstein2
commented
Dec 4, 2017
Contributor
Sorry for the radio silence. I've been a bit swamped, we are working with a contractor that will be able to take a look at it |
ContributorAuthor
@igorbernstein2 No worries. I just wanted our build to go back green. If This feature was prioritized by the Bigtable team, so feel free to take your time. (I.e. no one on the library side is feeling time pressured to land it.) |
theacodes
approved these changes
Dec 4, 2017
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
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 reverts commit 5a0e549 / PR #3811.
See: #3811 (comment)
/cc @calpeyser@igorbernstein2@sduskis
@igorbernstein2 I'll push a new branch that actually has the contents of #3811 in it and then we can change the base in #4443 from
masterto that branch? Then once #4443 is merged we can merge that branch back intomaster?