Repository navigation
Conversation
…int, not code unit searchTermRange computed "the last code point" via token.codePointAt(token.length - 1) — a code-UNIT index. For a token ending in a surrogate pair this reads the lone low surrogate rather than the true character. Most astral tokens happen to survive the resulting increment (the pair re-forms by luck), but a token whose low surrogate sits at the top of its range (0xDFFF) escapes the surrogate block on increment, and a token ending exactly at U+D7FF (the Hangul block boundary) increments straight into the surrogate range — both produce an invalid lone-surrogate bound that a UTF-8 binding mangles to U+FFFD, corrupting the inverted-index range scan for the term the user is still typing. Take the last character via spread (code-point iteration, not code-unit index) and increment its true code point. When the successor would itself be a surrogate value or exceed U+10FFFF, degrade to an exact match instead of a widened range — never wrong, merely narrower, and only reachable at those two boundaries. Added astral-prefix regression coverage in both consuming engines (@lunora/shard-engine, @lunora/sql-store) alongside the unit-level pins.
|
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: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (3)
📒 Files selected for processing (1)
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 |
|
Thank you for following the naming conventions! 🙏 |
|
Thank you for confirming the Contributor License Agreement! 🙏 |
❌ Deploy Preview for lunorash failed.
|
|
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. |
Branched before #288/#289 landed, so it needs a rebase onto current alpha before merge.
Commits
Files this branch still changes relative to alpha