giving up after 0 fragment retries
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 40
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
https://lbryians.slack.com/archives/CACSTN9SL/p1564664667305700
Should this say 0? From other things I read, it should have a value of 10.
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
Start with the linked Slack discussion and search the repository for the phrase "fragment retries" and the message about giving up after zero retries. Trace where that value is set and verify the finished behavior against the expected retry count described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100