adoptium / adoptium/api.adoptium.net
Get visibility on when GitHub rejects or rate limits when a user gets 302'd to them via the API
Open
enhancement
- Dominant language
- Kotlin
- Stars
- 44
- Forks
- 36
- Avg merge
- 5h 27m
- Merged PRs (30d)
- 42
Description
Our API 302's to GitHub which in turn relies on AWS S3 - we don't see the rate limiting or rejection chain
Contributor guide
Research direction
Start at the API entry point that returns the 302 to GitHub and trace how downstream GitHub and AWS S3 responses reach the user. Define which rate-limit and rejection details should be visible across that chain, then verify the behavior with the relevant API request path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, github, kotlin
- Domain
- api, cloud, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100