Keep response streams alive through connection failures (#37485)

## What changed

- Classify HTTP connection failures separately from other network errors without exposing request URLs.
- For sampling requests, retry connection failures with exponential delays from 5 to 60 seconds and show a `Reconnecting... waiting for network` stream error.
- Preserve the normal stream retry budget while waiting for the provider to become reachable. Keep the existing bounded retry behavior for other retryable errors.

## Testing

- Verify connection errors are classified without leaking URL contents.
- Verify a turn recovers after its provider becomes reachable and still applies the configured retry limit to a subsequent incomplete stream.

GitOrigin-RevId: 646553290c865a1332abd30c4a64ed9266bbfc6f
This commit is contained in:
jif authored and copyberry committed 2026-08-07 18:33:46 +00:00
1 parent 509565820f
commit 5a0d0929e2
10 files changed
+162 -12

No files matched your search

+3 -1
View File
@@ -29,7 +29,9 @@ impl RetryOn {
(self.retry_429 && status.as_u16() == 429)
|| (self.retry_5xx && status.is_server_error())
}
TransportError::Timeout | TransportError::Network(_) => self.retry_transport,
TransportError::Timeout
| TransportError::Connection(_)
| TransportError::Network(_) => self.retry_transport,
_ => false,
}
}