mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-07-16 05:43:54 +03:00
[Issue]: Secondary metadownloaders usually ignored on series matching. #4113
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Sorek on GitHub (Aug 13, 2022).
Please describe your bug
Issue: Jellyfin will use the first series metadownloader even on an extremely poor match. This happens even if a much better match exists on a secondary source.
Steps to Reproduce:
Expected Behavior: It will pick a perfect match over a poor one.
Jellyfin Version
Other
if other:
10.8.3
Environment
Jellyfin logs
No response
FFmpeg logs
No response
Please attach any browser or client logs here
No response
Please attach any screenshots here
No response
Code of Conduct
@1337joe commented on GitHub (Oct 9, 2022):
The plugin itself reports when it's found a match, Jellyfin just accepts the first provider (according to the configured ordering) that says it's got the item.
Does this happen with anything besides the anilist plugin as the first provider? I looked into an anilist-related bug report sometime last year and seem to remember finding that the anilist plugin has no logic to determine if what it finds actually matches the item so it just accepts the top search result and reports success.
@jellyfin-bot commented on GitHub (Feb 7, 2023):
This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.
If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.
This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.