fix: preserve chat state across archive transitions#482
Conversation
Compute removals across the combined active and archived chat lists so moving a chat between lists does not clear its composer draft or member cache. Fixes #466
|
Warning Review limit reached
Next review available in: 39 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. 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 Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
|
Ready to review this PR? Stage has broken it down into 2 individual chapters for you:
Chapters generated by Stage for commit 43bede0 on Jul 12, 2026 3:54am UTC. |
|
Closing because this PR's first CI run inherited the known master failure in messageMediaDiskCacheReadDeletionMaintainsTrackedFootprint. Master runs 29100021269 and 29149535840 are red; clean fix PR #464 is ready and green. Pip never merges a PR that has ever had red CI. After #464 merges, this branch can be rebased and a fresh draft PR opened. |
Summary
Verification
Fixes #466