fix(polymarket): project in-event Chainlink ticks - #305
Conversation
|
Warning Review limit reached
Next review available in: 18 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 Plus Run ID: 📒 Files selected for processing (6)
✨ 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 |
Change contract
Project causally valid Chainlink ticks from
[event_start - max_delay, event_end)into Polymarket research factors while preserving the pre-open-only audit and frozen settlement strike.Out of scope
Dependency / merge order
None. Based on current
mainafter #303. Issue #304 remains open until exact-main cloud snapshot acceptance succeeds.Focused validation
cargo +1.91 test --locked -p ploy-research— 288 library tests and 2 binary tests passed.cargo +1.91 clippy --locked -p ploy-research --all-targets --no-deps -- -D warnings— passed.sha256:e6357720e42c60311e65004d59647d1c1b70edb7d6ca90a1af15fcf5d7f22592, pinned by both BTC/SOL missions.git diff --checkand touched-file rustfmt checks — passed.Targeted counterexamples cover the exact event-window boundaries, carried rows, over-delayed rows, non-causal availability, and the production clock shape where the pre-open tick freezes strike while an in-event tick restores current-reference freshness.
Rollout / rollback impact
Research-only. Rollout requires a new exact-main research image and immutable cloud snapshot/readback. Rollback is a single-commit revert; the old fail-closed no-factor-observation behavior returns. No collector or runtime cutover is included.
Matt flow
Entered through
diagnosing-bugs, thentriage/issue #304, TDD implementation, and two-lanecode-review.Refs #304