fix: suppress repeated corrupt kanban backups#33319
Closed
Oceanswave wants to merge 1 commit into
Closed
Conversation
This was referenced May 27, 2026
19 tasks
Author
|
Closing because the upstream database hardening changes have now landed, so this duplicate Kanban corruption-backup retry PR is no longer needed. |
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.
Summary
Tests
Operational context
Observed a malformed board DB causing repeated backup/log spam from multiple gateway tick paths. This preserves the first backup for a specific corrupt file fingerprint and retries only after the DB file changes.
Fixes #32593