Repository navigation
feat(inference): backfill - #16
Merged
Merged
Conversation
BACKFILL_HOURS rewinds the cursor once per runtime volume so the stream re-predicts events of the last N hours; windows warm up before that point. A fresh incident service otherwise covers only channels with events after its start. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Jira
HACK-183
Changes
BACKFILL_HOURS(default 0 = off). Once per runtime volume (markerruntime/backfill.done) the cursor is rewound to the first event of the last N hours; the normal stream then re-predicts them in id order, so each channel ends with the prediction of its newest event. Expired ones (ts + horizon < now) are skipped as usual but still update windows.window + N hours, so rolling windows are full at the backfill start.inference-incidentstarted fresh on the stand and predicts only channels with events after its start (139 channels after 1.5 h).Rollout
Backend compose sets
BACKFILL_HOURS=30forinference-incident; the next restart runs it once (~200k events).Verification
test_backfill_predicts_recent_events_once: no prediction without backfill, one with it, none again after the marker.🤖 Generated with Claude Code