tx_signer: speculatively increment sequence on error #178
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
When encountering an error broadcasting a transaction, speculatively retry the operation once with an incremented sequence number. This is to handle the case where a transaction was successfully broadcast, but an error occurred returning the response. In such a case, the sequence number may be out-of-sync with the chain, so if we replay the transaction in such cases we may get it to succeed.
Codecov Report
@@ Coverage Diff @@
## develop #178 +/- ##
===========================================
- Coverage 22.83% 22.77% -0.06%
===========================================
Files 63 63
Lines 2444 2450 +6
===========================================
Hits 558 558
- Misses 1886 1892 +6
Continue to review full report at Codecov.
|
Merged
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 encountering an error broadcasting a transaction, speculatively retry the operation once with an incremented sequence number.
This is to handle the case where a transaction was successfully broadcast, but an error occurred returning the response.
In such a case, the sequence number may be out-of-sync with the chain, so if we replay the transaction in such cases we may get it to succeed.