mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
[10.8.0 - beta2] Metadata refresh starts a whole library scan instead of updating a single artist’s metadata. #3769
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 @derkington on GitHub (Apr 23, 2022).
Please describe your bug
Metadata refresh appears to start a whole library scan instead of updating a single artist’s metadata.
A fully library scan is started, you can hear the hard drives churning and it goes on for hours as you would expect. There’s nothing displayed visually in Jellyfin or in the logs that tell me what is happening. But you can see information on the console of the container.
The expected behaviour is only the information for that specific artist is updated, not the entire library, this is how it worked in Jellyfin 10.6.x. This issues seemed to be introduced in Jellyfin 10.7.x.
Jellyfin Version
10.8.0
if other:
No response
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
@jellyfin-bot commented on GitHub (Aug 22, 2022):
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.