-
Notifications
You must be signed in to change notification settings - Fork 10
Fix copy-db producing a silently corrupt, non-restorable database copy #2098
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
kriszyp
wants to merge
9
commits into
main
Choose a base branch
from
kris/copydb-silent-corruption
base: main
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
Show all changes
9 commits
Select commit
Hold shift + click to select a range
594b29f
Expose a reusable blob-root copy primitive and a copy README variant
kriszyp d577fb0
Stop copy-db from producing a silently corrupt, non-restorable copy
kriszyp abbd829
Address cross-model review: rollback, resume, cleanup and validation …
kriszyp 2178c52
Match house test style: plain assert, no sinon, setAuditRetention
kriszyp 5044a6c
Address copy-db review feedback
kriszyp b6c192c
Protect compaction target databases
kriszyp faf06aa
Fail closed on occupied compaction targets
kriszyp 8ea3ba0
Fix segment-unaware blob-root containment check, warn on missing conf…
kriszyp 162cc49
Widen blob-root containment check to every path a failure removes; cl…
kriszyp 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
Large diffs are not rendered by default.
Oops, something went wrong.
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.
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 (non-blocking): This test asserts the colliding database is registered (
getDatabases()['collision-source-copy']) before compacting. Both the oldcopyDatabaseRootStores/relative(...) === ''check and the newexistsSync(copyDest)check protect a registered database whose path matches exactly, so this test would still pass withfaf06aafb("Fail closed on occupied compaction targets") reverted — it doesn't exercise the gap that fix actually closed (an unregistered occupant at the target path: a stray leftover, a failed-to-load, or restore-blocked database, none of which appear ingetDatabases()). Consider adding/adjusting a case that writes an arbitrary file or directory atcopyDestwithout registering a database there, to prove the newexistsSync-based check (not just the old registration-based one) is what's guarding the path.