[codex] Make context stream Send#28
Conversation
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 19 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: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
Comment |
Summary
invoke_stream/invoke_stream_in_contextreturnSendstreamsSendWhy
OpenHuman drives agent turns inside
tokio::spawnand otherSendfuture boundaries. The v1.7.0 context stream API preserved caller context but returned a non-Sendstream, blocking the host cutover.Validation
cargo fmt --checktimeout 180s cargo clippy --all-targets -- -D warningstimeout 120s cargo test invoke_stream_in_context_stream_is_sendtimeout 120s cargo test invoke_stream_in_context_unsubscribes_channel_listener