Add retry to transport
Open
Nobody has claimed this yet.
enhancement
help wanted
- Dominant language
- Go
- Stars
- 1.5k
- Forks
- 152
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 6
Description
We get 502 and 504 occasionally from GitHub. These should be retried.
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 by locating the transport implementation used for GitHub requests. Done means 502 and 504 responses are retried; the issue does not name a file, entry point, or test, so the intended retry behavior and verification approach need to be established first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100