Repository navigation
Conversation
added 2 commits
October 24, 2026 13:47
A checkpoint can fold log entries the events bridge has not read yet; the bridge then detects a gap and skipped them, so consumers lost the push. Store the refs visible at the published seq in the cursor and, on a gap, diff them against the current refs and emit the missing create/update/delete events with the checkpoint seq (so (repo, seq, ref) dedup still holds on retry). Older cursors without refs keep the previous skip behaviour and are populated on the next successful pass.
This branch has not been deployed
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.
The events bridge tails the WAL from a durable cursor. When a checkpoint folds log entries before the bridge reads them (
maintenanceor an opportunistic push-triggered checkpoint),catch_updetects a gap and skipped the whole range: the entries are no longer readable, so a webhook consumer never sees the push (no CI, no search indexing, no outgoing webhooks).This stores the refs visible at the published seq in
events/cursor.jsonand, on a gap, diffs them against the current refs and emits the missingcreate/update/deleteevents with the checkpoint seq. The synthetic events go through the same sink path, so(repo, seq, ref_name)dedup still holds if the delivery is retried. Cursors written by older versions have no refs; the bridge keeps the previous skip behaviour for that first gap and populates the snapshot on its next successful pass.