fix: fall back from nonfinite Retry-After values

[Shubham-Padkonde]

Description

A malformed Retry-After header such as NaN, Infinity, or an overflowing numeric value currently reaches time.sleep/asyncio.sleep. This can replace the API error with a ValueError/OverflowError or leave an asynchronous retry waiting indefinitely.

Treat nonfinite numeric values as invalid headers and use the existing exponential backoff, just as for other unparseable Retry-After values. Valid numeric values and HTTP dates retain their behavior.

Six sync/async response regressions fail before the fix and pass afterward. The complete suite passes: 2,887 tests. Ruff and git diff --check pass.

Documentation

No public API or documentation changes required.

[greptile-apps]

Confidence Score: 5/5

[Medium risk] Changes retry logic for rate-limit handling.

The PR appears safe to merge; no actionable regression was identified.

Summary

The PR rejects nonfinite numeric Retry-After values so sync and async retries use exponential backoff instead of passing invalid delays to sleep.

• Adds regression tests for NaN, Infinity, and overflowing numeric headers in both request paths.

_{Reviews (1) · Last reviewed commit: "fix: fall back from nonfinite retry-afte..."}