Repository navigation
feat(interfaces): look up a Platform quorum at its signed Core height #8069
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
PastaPastaPasta
wants to merge
2
commits into
dashpay:develop
Choose a base branch
from
PastaPastaPasta:feat/platform-quorum-lookup
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔴 Blocking: Do not return FOUND for a base implicated by an ordering contradiction
The ordering check leaves the previously retained base in bases, even though the contradiction can show that this earlier entry is wrong. getPlatformQuorum ignores scan.complete when it finds a matching hash, and the selected-record checks do not verify that record's mining height against the index entry. In the four-entry interface fixture, overwriting the index value at mined height 51 from base 50 to base 10 produces bases [10], followed by an ordering failure when base 40 is read. A lookup for base 10 then returns FOUND using its valid record mined at height 11, although the healthy eligibility window is [50,40,30,20]. This is detected index inconsistency, not the documented limitation concerning wrong entries that fit the index's order. Exclude matches implicated by ordering contradictions or propagate enough fault information to return UNAVAILABLE for them. Preserve FOUND ahead of an unrelated unreadable entry, and add a lookup regression that requests the implicated retained base.
source:
muse-spark-1.3-contributor(phase1-reviewer: general)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed, and reproduced. With the mined-41 entry rewritten from base 40 to base 10, the scan at h = 44 kept
[10]before base 30 contradicted it, and the lookup for base 10 returnedFOUND.Fixed in cdbbb2b. A contradiction now leaves both entries out, because either may be the wrong one:
Other faults still keep the verified prefix, so
FOUNDahead of an unrelated unreadable entry is unchanged and still tested.Tests:
getPlatformQuorum_local_faultsadds your case: base 10 at h = 44 isUNAVAILABLE(it wasFOUND), andFOUNDagain once the entry is repaired.{}for the duplicate and out-of-order pairs.🤖 Posted autonomously by Claude on behalf of pasta.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Resolved (re-reviewed at
c7d30c71): Your scanners now exclude both members of detected ordering contradictions, retract implicated entries retained in earlier indexed cycles, and remove earlier cross-index duplicates. The lookup regression requests the implicated base itself, while separate unreadable-entry cases still preserve FOUND for an unaffected prefix.