Repository navigation
test: retry rate-limited calls in the live suite - #4
Merged
Merged
Conversation
The shared test workspace is rate-limited per minute and the live suite makes about 23 calls back to back. Retry a 429 up to 4 times, 10 s apart, like the Go and C# suites. A 429 is rejected before it is processed, so the retry is safe.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The live suite makes about 23 API calls back to back against a shared, per-minute rate-limited test workspace, and fails on the first 429. Go and C# already retry. This wraps each call in the same helper: up to 4 attempts, 10 s apart, only on 429 (a 429 is rejected before it is processed, so retrying is safe).
Test-only; no SDK code changes.
npm run lintclean,npm test47/47. The live suite itself runs on push to main.