Skip to content

Apply configured retries to HTTPS endpoint requests - #591

Open
betacatsling wants to merge 1 commit into
runpod:mainfrom
betacatsling:fix/https-retries
Open

Apply configured retries to HTTPS endpoint requests#591
betacatsling wants to merge 1 commit into
runpod:mainfrom
betacatsling:fix/https-retries

Conversation

@betacatsling

Copy link
Copy Markdown

RunPodClient mounts its retry adapter only for HTTP, while the normal RunPod endpoint URL uses HTTPS. A rate-limited HTTPS GET therefore fails immediately instead of using the configured retry policy.

Mount that policy for HTTPS as well. The regression runs real local HTTP and HTTPS servers that return 429 once, then 200. It verifies both responses are requested and the client succeeds, with TLS certificate verification enabled. On the unchanged base, HTTPS fails while the HTTP control passes.

Local validation: 634 unit tests passed, including the repository's coverage check; cloud E2E and performance tests were excluded. Black checked the new test and changed production line, and git diff --check passed. No RunPod resources or live provider calls were used.

AI assistance was used for implementation and local verification.

Fixes #590.

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.

Configured endpoint retries are not applied to HTTPS requests

1 participant