Apollo raises 429 errors when refreshing the adaptor list
Open
Nobody has claimed this yet.
bug
- Dominant language
- Jupyter Notebook
- Stars
- 5
- Forks
- 10
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 17
Description
For example:
The error occurs because we are hitting rate limits calling GitHub's servers to pull down adaptor metadata.
Solutions:
- Use a GitHub API token to increase the request limit
- Use another source
As an aside, in the current implementation if an adaptor receives a 429, it;ll be IGNORED by apollo like it doesn't exist. We are going to drop in a fix for this so that the error are less harmful .
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 Apollo's adaptor metadata refresh path and trace the calls to GitHub's servers. Reproduce or inspect the 429 handling, then verify that rate-limited adaptors are not silently treated as missing and that the selected rate-limit mitigation works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100