fix(engine): choose pre-entry opponent controller - #7382
Conversation
|
Warning Review limit reached
Next review available in: 1 minute You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. 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 (57)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
📝 Generate docstrings
🧪 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 |
|
Generated for head Parse changes introduced by this PR · 3 card(s), 5 signature(s) (baseline: main
|
…hase-rs#7382 Upstream phase-rs#7382 adds four lines in apply_action (@@ -9867,0 +9868,4 @@), entirely above the begin_pending_trigger_target_selection producer this census pins. The rebase raised the literal as a conflict on two lane commits and then drifted it SILENTLY at the tip, where the pinned line had become a bare `}`. Only the offset-from-enclosing-fn control caught the silent one: it is still 134, which is what re-establishes producer identity, since the same mint text occurs at several coordinates in this crate and the text alone cannot discriminate. The new value is measured in the rebased file, never computed from the shift. Assisted-by: ClaudeCode:claude-opus-5
…s new variant Upstream phase-rs#7382 added `WaitingFor::EntryControllerChoice { player, candidates }` (CR 614.12a), so the variant reach-guard moves 129 -> 130. Adjudicated on the terms this row already set for phase-rs#7336, not bumped: that variant's body holds no `DecisionTemplate`, so it is not a third carrier, and both the carrier vec and the redaction loop below it are unchanged. Only the reach-guard total moves. The number is read from this assertion's own failure output rather than from a hand-written variant counter -- one was tried and returned 49 while contradicting itself, and a second instrument that disagrees with the syn parse is worth less than no second instrument. This drift produced no merge conflict and could not have, so the reach-guard plus CI were the only things between it and shipping. Assisted-by: ClaudeCode:claude-opus-5
No description provided.