notary: fix "Condition never satisfied" in Notary test, fix #2422 #3337
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
The theory is: * we add a block * it triggers notary * which can process the fallback before we're to setFinalizeWithError * it'll fail and require an additional block to enter, but it's never added * FAIL The solution is: * always add an additional block, but treat the first fb specially Signed-off-by: Roman Khimov <[email protected]>
It checks for any transaction given (like fb), not exactly the main one. Signed-off-by: Roman Khimov <[email protected]>
AnnaShaleva
approved these changes
Mar 5, 2024
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.
The theory is:
The solution is: