`--ignore-errors` and `--max-retries` do nothing against `ConnectionRefusedError`
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.2k
- Forks
- 214
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I've tried Waybackpack, and the Internet Archive sometimes refuses connexions for apparently no reason, as the refused link can be openned in the browser.
I hoped that --ignore-errors would help Waybackpack ignore that error; and that --max-retries would retry to connect; but to no avail.
Best regards.
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 by tracing the CLI handling for --ignore-errors and --max-retries, then reproduce the ConnectionRefusedError against a refused connection. Done means the two options behave as described for that error, with tests covering both retrying and ignoring it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100