Repository navigation
fix(#120): MEDIUM: a shard backup copies a live WAL-mode SQLite with no quiesce step; resto - #431
Merged
Merged
Conversation
Db.createBackup now writes a consistent VACUUM INTO snapshot, checks it with integrity_check and renames it to webcalendar.db.backup with no raw-copy fallback, and a new worker (server/utils/dbBackup.js) writes it at production boot and then hourly, so the nightly shard backup always contains a whole copy. quiesceDatabase now fails when the checkpoint returns no result; this round changed no code because the earlier e2e failure did not recur (Playwright 76/76 twice, node 1768/1768), and the failing test name was not in the log, so the cause is unconfirmed. Refs #120 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Refs #120
Db.createBackup now writes a consistent VACUUM INTO snapshot, checks it with integrity_check and renames it to webcalendar.db.backup with no raw-copy fallback, and a new worker (server/utils/dbBackup.js) writes it at production boot and then hourly, so the nightly shard backup always contains a whole copy. quiesceDatabase now fails when the checkpoint returns no result; this round changed no code because the earlier e2e failure did not recur (Playwright 76/76 twice, node 1768/1768), and the failing test name was not in the log, so the cause is unconfirmed.
Driver gates (measured, not claimed)
red/green output
🤖 Generated with Claude Code