Commit 9f4fe67
Bound body read by per-request timeout (same class as Dart/Node fix)
reqwest's `Client::timeout` covers only the connect + initial-response
phase. The response body stream that backs `resp.text()` is not
covered — a slow or stalled body would otherwise hang the SDK call
indefinitely.
Same bug class as the Node SDK fix in ca0de42 and the Dart SDK fix
in 0e528c3. The Rust variant gets the same total-deadline treatment:
store the configured timeout on Transport and wrap `resp.text()` in
`tokio::time::timeout` so the body read is also bounded by it.
Verified locally: 25/25 unit + 2/2 doctests passing; clippy clean
under `-D warnings`.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>1 parent e9c6d9e commit 9f4fe67
1 file changed
Lines changed: 21 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
176 | 176 | | |
177 | 177 | | |
178 | 178 | | |
| 179 | + | |
179 | 180 | | |
180 | 181 | | |
181 | 182 | | |
| |||
211 | 212 | | |
212 | 213 | | |
213 | 214 | | |
| 215 | + | |
| 216 | + | |
| 217 | + | |
| 218 | + | |
| 219 | + | |
214 | 220 | | |
215 | 221 | | |
216 | 222 | | |
| |||
301 | 307 | | |
302 | 308 | | |
303 | 309 | | |
304 | | - | |
305 | | - | |
306 | | - | |
307 | | - | |
| 310 | + | |
| 311 | + | |
| 312 | + | |
| 313 | + | |
| 314 | + | |
| 315 | + | |
| 316 | + | |
| 317 | + | |
| 318 | + | |
| 319 | + | |
| 320 | + | |
| 321 | + | |
| 322 | + | |
| 323 | + | |
| 324 | + | |
308 | 325 | | |
309 | 326 | | |
310 | 327 | | |
| |||
0 commit comments