Generalize matching criteria for tombstone at boot up #31547
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
Codecov Report
@@ Coverage Diff @@
## master #31547 +/- ##
=======================================
Coverage 81.3% 81.3%
=======================================
Files 734 734
Lines 205284 205284
=======================================
+ Hits 167077 167084 +7
+ Misses 38207 38200 -7 |
Lichtso
approved these changes
May 9, 2023
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.
Problem
The tombstones fail to match at start up while running
ledger-toolSummary of Changes
The criteria to match against closed program is too restrictive. The tombstones were of
LoadedProgramType::FailedVerificationtype. This PR generalizes the check to match against any type of tombstone.Fixes #