Investigate and possibly implement more efficient interaction with GitHub
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
In #410 we implemented a throttling mechanism for dialing back the number of GitHub requests that Rosetta makes when it gets close to max per-hour API interaction limit. One thing we did not do was investigate whether we could do fewer of these API calls in general and thus make it so that we would hit this limit less often. I have seen the warning message that is shown to the user when the throttling is happing twice in the last couple of days, one because of testing that I was doing, but the other probably just due to normal translator interactions. We should probably take some time to see if the interaction can be made more efficient so that the throttling is less likely to kick in.
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
No files or tests are named. Start by reviewing #410 and the warning about GitHub API throttling, then trace the requests made during normal translator interactions; done means identifying whether calls can be reduced and documenting or implementing a justified improvement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, typescript
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100