fix(drive): order ascending cursor range bounds#4148
Conversation
|
Warning Review limit reached
Next review available in: 59 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: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ 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 for review — 24 ahead in queue (commit 9f62a35) |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## v4.1-dev #4148 +/- ##
============================================
+ Coverage 87.43% 87.45% +0.01%
============================================
Files 2646 2648 +2
Lines 333981 334236 +255
============================================
+ Hits 292023 292304 +281
+ Misses 41958 41932 -26
🚀 New features to boost your workflow:
|
What
Why
The previous endpoint order produced reversed GroveDB ranges for ascending queries whose cursor was below the predicate bound. The proof and no-proof paths share this construction, so correcting it restores the query semantics at their common boundary.
This covers PLATFORM-DS-CAND-388.
Checks