Skip to content

harness(openai): surface the full transport error source chain#50

Merged
senamakel merged 1 commit into
mainfrom
harness/openai-transport-error-chain
Jul 10, 2026
Merged

harness(openai): surface the full transport error source chain#50
senamakel merged 1 commit into
mainfrom
harness/openai-transport-error-chain

Conversation

@senamakel

Copy link
Copy Markdown
Member

Summary

send_checked mapped a reqwest send failure with a plain {e}, which renders only the outermost context (error sending request for url (...)). The actionable cause — connection refused (os error 111), a TLS failure, a DNS error — lives one or more links down the source() chain and was dropped.

Add error_source_chain(err) which walks the full source() chain joined by ": ", and use it when mapping the transport failure. This lets a downstream host classify on the TinyAgentsError::Model message (loopback-offline detection, transport retryability) — parity with what a host that kept the raw reqwest::Error chain could do.

Commands run

  • cargo fmt --check
  • cargo test --lib openai:: — 62 pass
  • cargo clippy --lib -- -D warnings — clean

Behavior

Additive; the only change to existing output is a richer transport-error message (now includes the cause chain).

A reqwest send failure renders only its outermost context in Display (e.g.
"error sending request for url (...)"), while the actionable cause — a
"connection refused (os error 111)" errno, a TLS failure, a DNS error — lives
one or more links down the source() chain. send_checked stringified just {e},
so a host classifying on the TinyAgentsError::Model message (loopback-offline
detection, transport retryability) could not see it.

Add error_source_chain(err) which walks the full source() chain joined by ": ",
and use it when mapping the send failure. Unit-tested; fmt + clippy clean.
@coderabbitai

coderabbitai Bot commented Jul 10, 2026

Copy link
Copy Markdown

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 28 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 1e794796-2d94-4780-8312-632bd67c2f65

📥 Commits

Reviewing files that changed from the base of the PR and between 7c6e81a and b818378.

📒 Files selected for processing (3)
  • src/harness/providers/openai/mod.rs
  • src/harness/providers/openai/test.rs
  • src/harness/providers/openai/transport.rs

Comment @coderabbitai help to get the list of available commands.

@senamakel senamakel merged commit b580f1a into main Jul 10, 2026
3 checks passed
@senamakel senamakel deleted the harness/openai-transport-error-chain branch July 10, 2026 21:11
senamakel added a commit that referenced this pull request Jul 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant