hydrusnetwork / hydrusnetwork/hydrus
Allow Parsers to Fall Back to Lower Ranked URLs on Error
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.2k
- Forks
- 207
- PR merge metrics
- No merged PRs in 30d
Description
So, this request is already out there, but I wanted to make sure it's in the new system.
So, the idea is basically that, sometimes, an API might be horrible, and might produce 404's or 403's for reasons, and sometimes, in these situations, there can be alternate options that might work or might not, but there's no good way to know what will or won't work at any given moment. In these admittedly rare instances, an option to fall back and use the first functional download would be great.
EDIT: Relevant ask from back in May: https://hydrus.tumblr.com/post/617669264412966912/hey-its-the-guy-making-that-google-drive
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
The issue names no files, tests, or entry points. Start by locating parser URL ranking and download error handling, then determine how alternate URLs are represented and how a successful fallback would be tested. Done means defining the fallback behavior and covering failures such as HTTP 404 and 403.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100