fix: fix cucumber transaction builder reliability #3147
Merged
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
SWvheerden
force-pushed
the
sw_cucumber_tx
branch
from
4c0c8e4 to
ab7a431
Compare
stringhandler
approved these changes
Jul 29, 2021
|
PR queued successfully. Your position in queue is: 1 |
stringhandler
changed the title
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.
Description
We sometimes find that transactions created by the cucumber transaction builder fail lmdb insertion by duplicate excess.
This increases the private key range for the private keys increasing the range of the excess. This should decrease duplicate entries.
Motivation and Context
How Has This Been Tested?
Checklist:
developmentbranch.