Skip to content

Conversation

@wedamija
Copy link
Member

Currently, the skip backfill logic is causing us to not write misses a lot of the time. I'm updating this logic so that we:

  • Store a timestamp after we update the interval
  • If the last_update_ms timestamp occurred before the update, then skip the backfill, since we can assume that any misses there are caused by the change in interval.

…as been changed

Currently, the skip backfill logic is causing us to not write misses a lot of the time. I'm updating this logic so that we:
 - Store a timestamp after we update the interval
 - If the last_update_ms timestamp occurred before the update, then skip the backfill, since we can assume that any misses there are caused by the change in interval.
@wedamija wedamija requested a review from a team as a code owner January 12, 2026 22:52
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Jan 12, 2026
Comment on lines +199 to +206
assert timestamp_ms is not None
assert int(timestamp_ms) > 0

now_ms = int(datetime.now(timezone.utc).timestamp() * 1000)
assert abs(now_ms - int(timestamp_ms)) < 60000 # Within 60 seconds

def test_no_interval_change_no_redis_timestamp(self) -> None:
"""Verify that updating without changing interval does not set Redis timestamp."""

This comment was marked as outdated.

@wedamija wedamija enabled auto-merge (squash) January 13, 2026 17:40
@wedamija wedamija merged commit 85934ec into master Jan 13, 2026
66 checks passed
@wedamija wedamija deleted the danf/uptime-fix-skipped-miss-backfills branch January 13, 2026 18:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants