Skip to content

Fast-forward last_poll_ts on startup (#74) - #75

Merged
IceRhymers merged 1 commit into
masterfrom
issue-74-startup-fast-forward
Mar 31, 2026
Merged

Fast-forward last_poll_ts on startup (#74)#75
IceRhymers merged 1 commit into
masterfrom
issue-74-startup-fast-forward

Conversation

@IceRhymers

Copy link
Copy Markdown
Owner

Summary

  • Fast-forwards last_poll_ts for all active sessions to the current timestamp during _resolve_startup_identity(), preventing re-processing of old messages after a restart
  • Reuses existing get_active_sessions + update_last_poll_ts — no new DB functions
  • Adds unit test test_startup_fast_forwards_last_poll_ts verifying the behavior

Closes #74

Test plan

  • RED: new test fails before implementation (update_last_poll_ts call_count == 0)
  • GREEN: new test passes after adding 6 lines to _resolve_startup_identity
  • Full suite: 285 passed (284 existing + 1 new), 0 failures

🤖 Generated with Claude Code

…sages

After resolving Slack identity in _resolve_startup_identity, fast-forward
last_poll_ts for all active sessions to the current timestamp so the first
poll cycle only sees messages posted after startup.

Closes #74

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@IceRhymers
IceRhymers merged commit 9b5aadb into master Mar 31, 2026
1 check passed
@IceRhymers
IceRhymers deleted the issue-74-startup-fast-forward branch April 3, 2026 14:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix: fast-forward last_poll_ts on startup to prevent re-processing old messages

1 participant