ABCI: Fix ReCheckTx for Socket Client#6124
Merged
mergify[bot] merged 4 commits intomasterfrom Feb 17, 2021
Merged
Conversation
Codecov Report
@@ Coverage Diff @@
## master #6124 +/- ##
==========================================
+ Coverage 60.65% 60.78% +0.13%
==========================================
Files 276 276
Lines 25646 25649 +3
==========================================
+ Hits 15555 15592 +37
+ Misses 8469 8437 -32
+ Partials 1622 1620 -2
|
tessr
reviewed
Feb 17, 2021
melekes
approved these changes
Feb 17, 2021
tessr
approved these changes
Feb 17, 2021
Co-authored-by: Tess Rinearson <tess.rinearson@gmail.com>
alexanderbez
pushed a commit
that referenced
this pull request
Feb 18, 2021
4 tasks
This was referenced Apr 22, 2022
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.
Fixes the race condition between a callback being set and called during ReCheckTx. Note, I do not see equivalent logic in the gRPC client (anymore) as #5439 suggests, so only the socket client was updated.
closes: #5439