Fix #376: Assert BitmapNeighborProvider backend invariant#587
Conversation
|
Warning Review limit reached
More reviews will be available in 49 minutes and 23 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ 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 |
Release Preflight
If you tag this commit as |
|
@codex Code Lawyer Activity Summary
Validation:
|
What changed
Replaced the unreachable
hasNode()fallbackfalsewith an explicitIndexErrorinvariant guard and added focused coverage for that impossible route.Why
The old tail branch made an invalid backend state indistinguishable from a real missing node. The provider now fails closed if readiness says a backend exists but routing cannot find one.
Closes #376
Validation
npx vitest run test/unit/domain/services/BitmapNeighborProvider.test.tsnpm run typecheck:src -- --pretty falsenpm run typecheck:test -- --pretty false