fix: handle non-integer Retry-After values in GraphQL retry

[abhi-0203]

Summary

Fixes #18 — int(retry_after) raises ValueError when Retry-After header is a decimal (e.g., "2.0") or HTTP-date. This PR uses float() with a fallback to 1.0, covering both integer and decimal values. If parsing fails, it defaults to 1 second.

Changes

• _handle_429_retry_sync: replaced int(retry_after) with float() + try/except
• _handle_429_retry_async: same for async sleep

Testing

• Verified with float("2.0") and float("2") both work.
• Verified fallback when header is missing or invalid.

Related

• Issue int(retry_after) raises ValueError on a non-integer Retry-After value #18 (the Retry-After parsing bug)
• Issue Retry-After is never read on 429 retries: dict(httpx.Headers) lowercases the key #17 (header lookup bug) — this PR does not address that; it only fixes the parsing error that would be exposed once Retry-After is never read on 429 retries: dict(httpx.Headers) lowercases the key #17 is fixed.

Closes #18

[github-actions]

Thanks for your interest. This repository does not accept contributions, so we've closed this PR.

To report a bug, request a feature, or share feedback, please post in the Shopify dev community forums

We triage in the forums, not in this repo. PRs and issues here are closed without review.

For more details see CONTRIBUTING.md.