Repository navigation
fix: nonfatal app db backup fail - #7965
Merged
Merged
Conversation
IMB11
commented
Oct 14, 2026
IMB11
commented
Member
- If the VACUUM INTO fails, we just copy the db files using tokio and continue, some corruption is automatically resolved when migrations run
- e.g going from 0.15 -> 0.21 app version
Contributor
Pull request changelogAppAddedChangedDeprecatedRemovedFixed
SecurityWebsiteAddedChangedDeprecatedRemovedFixedSecurityHostingAddedChangedDeprecatedRemovedFixedSecurity |
aecsocket
approved these changes
Oct 14, 2026
|
Queued — the merge queue status continues in this comment ↓. |
Merge Queue Status
This pull request spent 13 minutes 45 seconds in the queue, including 13 minutes 9 seconds running CI. Required conditions to merge
|
6 of 10 tasks
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
2 participants
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.