Repository navigation
fix: refresh private report history within one bounded run - #289
Merged
Merged
Conversation
Contributor
|
🦞👀 Pull request received. I will update this pull request when review starts. |
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.
Problem and change
Unchanged or empty Discord channels can retain stale observed checkpoints without proving a complete report window. The publisher now performs the normal guild-wide latest refresh, followed by the native bounded full/since scan for a pinned private selector policy, within one shared 1,200-second acquisition budget.
The policy is fetched from an isolated private ref and verified by exact commit, content hash, schema, configured guild, and bounded target set before restoring state. Both acquisition phases use the existing native collector. Failed acquisition preserves committed progress in the full private checkpoint only after the task-owned process group has been reaped; it does not publish the archive.
This also removes cloud export/upload from this publisher and temporarily removes schedules. Manual dispatch remains available. Recurring publication and cadence will be restored only after a measured full-size private checkpoint and acquisition run; this source change does not claim operational recovery or complete source coverage.
Validation
The branch includes the already-landed checkpoint diagnostics from #288. Full-size checkpoint recovery and the first measured acquisition remain separately gated.