palantir / palantir/go-githubapp
Add rate limiting retry middleware
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 450
- Forks
- 70
- Avg merge
- 14h 23m
- Merged PRs (30d)
- 26
Description
It would be helpful if the client creator provided an option to enable delays and retries in case of rate limiting. This should be optional because GitHub's hourly buckets mean you might have to wait a long time to try again. This also implies there should be an option for a maximum wait time, so if the retry header is past this value, the request can fail immediately. I expect this will be most useful if accidentally hitting the abuse limits (where the wait time is probably minutes), but could also be useful for regular limits.
Contributor guide
No contributing guide indexed for this repository
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 by locating the client creator and the request middleware or entry point that handles GitHub responses. Trace how rate-limit and retry headers are exposed, then define the optional delay/retry behavior and maximum-wait failure case. Done means existing requests remain unchanged unless enabled, and waits beyond the configured maximum fail immediately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, go
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100