Handle rate limit
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
Currently rate limit is not being handled at all. Which causes a build from scratch. It would be worth waiting for XX seconds (let's say below <60s) instead of building from scratch as it would still be faster for mid-size/large codebases.
Run actions/cache@v5
Warning: You've hit a rate limit, your rate limit will reset in 18 seconds
Warning: Failed to restore: Failed to GetCacheEntryDownloadURL: Rate limited: Failed request: (429) Too Many Requests: rate limit exceeded
Cache not found for input keys: goofy-b41b01ad3312fe1358359b7522c43860bfdad754166c7f1d385e51766e57b4c0
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the actions/cache@v5 restore path and trace how the shown 429 rate-limit response is handled. Done means a rate-limit reset below 60 seconds causes the action to wait and retry rather than immediately rebuilding from scratch; use the reported warning as the observable case to verify.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100