Repository navigation
Conversation
…mpty results .near()/.within() accepted transposed corners, antimeridian-crossing boxes, and non-finite/non-positive radii verbatim, each producing a silently empty result set after paying for a full covering scan. Validate in createGeoBuilder and throw BAD_REQUEST instead. Behavior change: a transposed or Pacific-spanning bounding box, or an invalid radius, now throws where it previously resolved to []. The antimeridian case is rejected rather than split into two queries — the error message tells callers to split at ±180 themselves.
…/patchMany
Under .rls("required"), guardWriter resolved the owning table of every bare
id in deleteMany/patchMany one at a time, each a fresh UNION-ALL probe over
every non-global table. Widen the TableOfId seam with an optional batch
resolver (tablesOfIds) and add locateTablesByIds, a chunked id-IN(...) probe
that resolves a whole batch in as few statements as possible.
The guard's per-id decision is unchanged — same probe, batched. The D1/
.global() twin needs no change: guardByIds falls back to the existing
per-id loop when no batch resolver is supplied. Bench: batched probe is
~4.6x faster than the per-id loop for 50 bare ids on an 8-table schema
(packages/do/__bench__/lookup-by-id-probe.bench.ts).
|
Warning Review limit reached
Next review available in: 55 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: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (3)
📒 Files selected for processing (3)
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 |
❌ Deploy Preview for lunorash failed.
|
|
Thank you for confirming the Contributor License Agreement! 🙏 |
|
Thank you for following the naming conventions! 🙏 |
|
Closing: this PR was opened in error by an automated run, outside the scope of its task. No work is lost — the branch is retained on origin and this PR can be reopened at any time. Context: this branch predates the merges of #288 and #289, so much of its content is already on |
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Work from an agent worktree, pushed under a descriptive name (local branch was
worktree-agent-aee0c271830bd31da).Branched before #288/#289 landed, so it needs a rebase onto current alpha before merge.
Commits