test(rfc0024): red — all seven §5 stubs land, status drafted→red - #359
Conversation
Stubs live with the invariant owners (.1/.2/.7 bench, .3 parquet, .4/.5 miner, .6 querier). Also pins the §7.2 open question: the generators live in a new dev-only crates/ourios-testgen (ourios-bench cannot host them without a dev-dependency cycle through the querier), named by the RFC per the CLAUDE.md §7 new-crate rule. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 14 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 (5)
✨ 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 |
There was a problem hiding this comment.
Pull request overview
This PR advances RFC 0024 to the “red” gate by landing ignored todo!() test stubs for each §5 acceptance criterion and updating the RFC text to reflect the intended generator strategy/module placement.
Changes:
- Update RFC 0024 status from
drafted→red, and revise the generator-home decision text. - Add ignored red-gate stub tests for RFC0024.1–.7, distributed across the owning crates (
ourios-bench,ourios-parquet,ourios-miner,ourios-querier). - Add a calibration/adversarial “scenario placement map” test module in
ourios-bench.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| docs/rfcs/0024-otlp-envelope-property-testing.md | Marks RFC as red and updates generator-home narrative in §3.2 / open-questions list. |
| crates/ourios-bench/tests/rfc0024_calibration.rs | Adds ignored stubs for calibration (.1/.2) and adversarial umbrella (.7), plus scenario ownership mapping. |
| crates/ourios-parquet/tests/rfc0024_properties.rs | Adds ignored stub for P1 round-trip fidelity (.3). |
| crates/ourios-miner/tests/rfc0024_properties.rs | Adds ignored stubs for P2 no-silent-merge (.4) and P3 bounds (.5). |
| crates/ourios-querier/tests/rfc0024_properties.rs | Adds ignored stub for P4 query-oracle property (.6). |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The #353 red-stub pattern for RFC 0024: seven
#[ignore]dtodo!()stubs placed with the crates that own each invariant —.1/.2/.7(calibration + the adversarial umbrella) inourios-bench,.3(P1 round-trip) inourios-parquet,.4/.5(P2/P3) inourios-miner,.6(P4 query oracle) inourios-querier— each naming its green slice.Also settles the RFC's §7.2 open question in §3.2: generators live in a new dev-only
crates/ourios-testgen(hosting them inourios-benchwould create a dev-dependency cycle throughourios-querier), named by the RFC per theCLAUDE.md§7 new-crate rule. Status ridesdrafted → redon the maintainer's drive-the-RFC go. Defaultcargo teststays green.🤖 Generated with Claude Code