Fix pagination issue caused by missing fillTheGap call#6055
Conversation
SDK Size Comparison 📏
|
WalkthroughUnconditionally runs the gap-filling routine after successful online channel queries in Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes
Poem
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: Repository UI Review profile: CHILL Plan: Pro Disabled knowledge base sources:
📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)
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 |
|



🎯 Goal
We need to call fillTheGap even on regular pagination, because we could have previously upserted a message out-of-order in the list (from a WS event). So fill the gap is required to fill the missing messages between the loaded messages, and the out-of-order upserted message.
Note: This is just a revert of a recently introduced regression, it will be fixed properly in the next regular release.
🛠 Implementation details
Revert the change from this optimisation PR
🧪 Testing
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.