feat(research): defer unresolved factor outcomes - #140
Conversation
|
Warning Review limit reached
Next review available in: 42 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: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughMission configs pin new search policy snapshots. Factor observation construction now offers labeled and unlabeled modes, retaining unresolved observations with ChangesFactor Observation Updates
Estimated code review effort: 3 (Moderate) | ~20 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
69aed95 to
a7e1976
Compare
a7e1976 to
4dd4ebd
Compare
Change contract
Add a crate-private unlabeled factor builder so verified-artifact snapshot code can emit unresolved rows without changing the public labeled builder behavior.
Out of scope
Dependency or merge order
mainFocused validation
settlement_up = NaNand no official resolution timestamp.Rollout / rollback impact
Low. This is a research-only internal seam. Rollback is a straight revert of this PR if the downstream adapter does not need the unlabeled path.
Summary by CodeRabbit
New Features
Bug Fixes
Configuration