test(server): RFC0003.16 red gate + scenario prose polish - #140
Conversation
|
@coderabbitai review |
|
Warning Review limit reached
More reviews will be available in 4 minutes and 3 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 Plus 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 |
✅ Action performedReview finished.
|
There was a problem hiding this comment.
Pull request overview
Adds the RFC0003.16 “served-binary” red-gate integration-test stub for ourios-server and polishes the corresponding scenario prose in the OTLP receiver RFC, aligning the spec text with the intended end-to-end contract and the verification process’ two-loop model.
Changes:
- Refines RFC0003.16 scenario prose to clarify HTTP listener wording and shutdown durability semantics.
- Adds an ignored (
#[ignore])ourios-serverintegration-test stub for RFC0003.16, greppable and ready to be flipped to a real socket test in the implementation PR.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| docs/rfcs/0003-otlp-receiver.md | Prose tweaks to RFC0003.16 scenario clauses (HTTP listener wording + shutdown semantics). |
| crates/ourios-server/tests/rfc0003_16_served_binary.rs | New red-gate ignored integration-test stub for RFC0003.16 served-binary scenario. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Red-gate step for the served-binary slice (docs/verification.md §3 two-loop): an #[ignore]'d ourios-server integration stub for RFC0003.16, greppable to the scenario, flipped by the implementation. Also folds in the two trailing Copilot prose nits on the RFC0003.16 scenario (from #139): the HTTP-listener Given clause now reads "bound on its configured port (default 4318)" (was missing the noun), and the shutdown bullet drops the contradictory "in-flight, already-fsync'd" phrasing for "no already-acked batch is lost on the way out". No semantic change. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
f2e293d to
8645ec1
Compare
What
RFC0003.16 red gate (the served-binary slice,
docs/verification.md§3 two-loop) — an#[ignore]'dourios-serverintegration stub for the served-binary scenario, greppable toRFC0003.16. The implementation PR flips it to a real-socket test (spawn the binary on127.0.0.1:0, export over real gRPC + HTTP clients, signal shutdown, thenWal::replay).Also folds in the two trailing Copilot prose nits on the RFC0003.16 scenario from #139 (now merged):
No semantic change to the scenario.
Verification
cargo test -p ourios-server --test rfc0003_16_served_binary→ 1 ignored (red gate). ·cargo clippy --all-targets -- -D warnings✓ ·cargo fmt --all --check✓ ·mdbook build✓Next
The implementation PR wires the receiver as a config-toggled
ourios-serverrole (axum::serve+tonicServeron the runtime, singleWalshared by both listeners, SIGINT graceful shutdown), flips this stub, and adds a confirming 405-on-non-POST test (per the OTLP review).🤖 Generated with Claude Code