[BUG] Import into a same-work pocket fails with an exception when the author has no root folder for that media type
Maintainers usually reply within 7 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
Research direction
Start by tracing the same-work pocket match and the path builder that throws when the target author lacks a root folder for the target media type. Check how the behavior in issues #213 and #219 relates to this case. Done when the import is rejected with an actionable reason or uses the default root, without throwing.
Written by the indexing model from the issue text.
Description
Problem
When a completed download is accepted into a same-work pocket of the other media type (#213), the target author may have no root folder for that media type (on one live library 302 authors had only an ebook root and 509 only an audiobook root). The import then throws No root folder configured for quality type: ... from the path builder instead of being rejected with a clear reason.
Suggested fix
Check for a root folder for the target media type when deciding the pocket match and reject with an actionable message (or fall back to the default root for that media type; #219 fills the missing root for newly added authors). Found while reviewing #213.
- Dominant language
- C#
- Stars
- 664
- Forks
- 48
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 1
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from Chaptarr/chaptarr
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 7 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 7 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Chaptarr/chaptarr#313 · 1 comment ·
Maintainers usually reply within 7 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 7 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 7 days
All issues in Chaptarr/chaptarr
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
unoplatform/uno.check#591 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
weaviate/csharp-client#378 ·
-
agentic-workflows automated testing
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Azure-Samples/Legacy-Modernization-Agents#194 ·
Maintainers usually reply within 1 day
-
area-encryption area-security p1-recommended technical-debt
Difficulty 2/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
V5: `asAllDay` parameter not working in `/feed/v5/calendar/sonarr.ics`Possibly taken @stevietv claimed this today. Openneeds-triage
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day