Concurrent retries
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 366
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
Hi Thanks for sharing this. What are your thoughts on implementing concurrent retries. We could make it go to a buffered channel on success and break/return as soon as that channel receives something.
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 file, test, or entry point is named in the issue; begin by reading the retry package and its existing tests to understand the current retry flow. The requested behavior is not specified enough to define completion, so clarify the concurrency model and success and termination semantics before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100