Clean up five follow-ups from the mobile hardening pass - #955
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
|
Warning Review limit reached
Next review available in: 22 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 selected for processing (20)
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 |
Five independent items surfaced while shipping the mobile connection work. Each was verified as a real defect, not a test artifact.
1. Deep-link scope validation (fixes 2 long-failing tests)
testDeepLinkRouterDropsInvalidOptionalHttpsPrScopeandtestDeepLinkRouterRejectsMalformedCrossMachineScopehave been failing on clean main for a while — 7 assertions across both — which masked regressions in every iOS lane this session. The tests were right: the router accepted anaccountMachineKeyof"not valid"(with a space) and anitemIdof"/". Scope components are now rejected when empty, whitespace-bearing, path-separator-bearing, control-character-bearing, or oversized, while staying opaque-ID compatible.2. Desktop paired-runtime endpoint memory
DesktopPairedMachineEndpointStaterecorded successes only — the same gap #948 closed on iOS, where dead endpoints get retried forever at the front of the queue. Now mirrors iOS: consecutive-failure tracking, demotion after two failures inside 120s, never removal, reset on success.3. iOS never told the relay it went to background
AccountService.swifthardcodedappForeground: true, so phone presence only aged out by timeout. Real lifecycle transitions now ride the existing presence path — no new timers.4. TUI polled lane status every second while streaming
tuiClient/adeApi.tsranlane.list {includeStatus:true}every 1s while streaming. Now a cheap fast poll with full status every 30s, plus a targeted fetch that keeps the focused lane fresh — the same split #947 built for desktop.5. Flaky file-service teardown
Intermittent CI failure
ENOTEMPTY: rmdir '/tmp/ade-file-service-tree-*/.git'(hit this PR stack once). Teardown is now recursive-forced with bounded retry rather than the assertion being deleted.Verification
🤖 Generated with Claude Code