-
Notifications
You must be signed in to change notification settings - Fork 0
Resume incremental pulls within event pages #177
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+268
−3
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟡 Checkpoint skip logic drops 404-to-delete transitions for paths sorting before the checkpoint
When resuming from a checkpoint with
Phase="changed", paths that sort lexicographically before or equal tocheckpoint.Pathare skipped entirely (line 2986). However, in the original (failed) run, some of those skipped paths may have received a 404 fromReadFileand been added to the localdeletedmap (line 2996) — without updating the checkpoint (since the checkpoint only advances on successfulapplyRemoteFile). Because the delete phase (deletedPathsloop at line 3024) only runs AFTER the changed loop completes, and the changed loop errored out before completing, those 404-redirected deletes were never applied.On resume, the skipped paths are never re-read via ReadFile, so they're never re-added to the
deletedmap. The local file persists as stale until the next periodic full pull.Example scenario
changedPaths (sorted): [A, B, C, D]
On resume (checkpoint.Path = B):
A's local file persists indefinitely (until next full pull).
This is a regression: without checkpoints, the entire page was retried and the 404 would be re-encountered, properly routing the file to deletion.
Prompt for agents
Was this helpful? React with 👍 or 👎 to provide feedback.