PRT-292 incorrect account sequence no payments to providers #253
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.
What kind of change does this PR introduce? (Bug fix, feature, unit tests, docs update, ...)
Retry mechanism for sequence number errors on payment requests by the expected sequence number.
Also, splitting the payment requests into a random block in an epoch instead of all payment requests on the first block.
What is the current behavior? (You can also link to an open issue here)
currently fails and doesnt parse the errors correctly and always asking rewards on the first block in an epoch
What is the new behavior (if this is a feature change)?
Retry mechanism for sequence number errors on payment requests by the expected sequence number.
Also, splitting the payment requests into a random block in an epoch instead of all payment requests on the first block.
Please describe what manual tests you ran, if applicable
testing multiple payment requests from the same provider in different processes, resulting in reproducing the problem and fixing it
Other information: