fix(database): reconcile chat session activity and state version - #68
Conversation
|
Warning Review limit reached
Next review available in: 16 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Gavel summary
Totals: 0 passed · 0 failed · 0 skipped · - |
868bf50 to
0527e18
Compare
Gavel summary
Totals: 3541 passed · 0 failed · 10 skipped · 2m59s |
last_activity_atis a high-water mark. The activity trigger and transcript ingest preserve that invariant, buttouchChatSessionassigned the current time directly and could move it backwards.This changes the chat writer to use the same monotonic semantics as the other writers.
touchChatSessionalso attempted to incrementstate_version, but the session state trigger always discarded that increment because no state fields changed. The ineffective write is removed, preserving the existing optimistic-concurrency behavior.Tests cover both contracts: chat activity cannot move backwards, and a chat touch does not advance
state_version.Closes #57