Repository navigation
Backport release/v6.7: Refuse pinned write modes that disagree with persisted migration
#4503
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
Merged
Merged
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
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.
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.
suggestion — (Also raised by codex.) Accepting
MemiavlOnlyfor every pin also lets through a store with real memiavl history and no migration, such as a pinned EVMMigrated or AllMigratedButBank node whose memiavl is at version > 0 while flatkv derives MemiavlOnly (freshly seeded, or rolled back below activation). Such a node then runs steady-state routing over a flatkv that never received the migrated data. Those two pins already open memiavl, somemIAVL.Version() > 0combined with a MemiavlOnly derivation is evidence you can refuse on; FlatKVOnly never opens memiavl and would need some other provenance signal.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.
@seidroid can you approve the PR
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.
Claude finished @alexander-sei's task in 12s —— View job
Approval request
I can't approve this PR. For security reasons this integration can't submit formal GitHub PR reviews, including approvals. All I can do is reply in this comment. The FAQ has more on this and possible workarounds.
Some context that may help:
release/v6.7needs more, a second maintainer has to approve it.Rollbackreturns an error after both backends have already been rolled back on disk.MemiavlOnlyfor every pin lets through a pinned node that has memiavl history but no migration (store.go:512).None of these stops a backport that matches #4484. They are better handled as follow-ups on
main.