Repository navigation
Continue verified home backup purges on their provider deadline - #382
Merged
Chris Eckert (ceckert) merged 1 commit intoNov 21, 2026
Merged
Conversation
Signed-off-by: Chris Eckert <christopher.k.eckert@gmail.com>
Chris Eckert (ceckert)
deleted the
codex/continue-restored-backup-purge
branch
November 21, 2026 21:37
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.
A normal TEST restore activated cleanly with the original home and enabled schedule. After authorizing backup deletion, the successful provider progress response was classified as a third transient failure and delayed the next confirmation by 480 seconds.
Use the durable operation watch timer to resume the authenticated backup release after 30 seconds when the provider reports that deletion is still converging. Keep the same snapshot custody until both the live and recoverable copies are absent. Readiness checks, ownership proof, and error handling keep their existing policy.
The regression proves repeated live and recoverable deletion progress does not spend failure attempts or extend the wait. Fake-clock coverage proves the exact due wake after a watch resync. Local typecheck, scoped lint, and 219 focused tests passed.