starred/jellyfin
1
0
Fork 0
mirror of https://github.com/jellyfin/jellyfin.git synced 2026-07-16 05:43:54 +03:00
Code Issues 822 Packages Projects Releases 17 Wiki Activity

[PR #14259] [MERGED] fix(collection): Do not lock newly created collections #13911

New Issue
Closed
opened 2026-02-07 07:21:11 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-07 07:21:11 +03:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/jellyfin/jellyfin/pull/14259
Author: @darioackermann
Created: 6/9/2025
Status: ✅ Merged
Merged: 6/10/2025
Merged by: @crobibero

Base: master ← Head: dac/fix-collection-locking

📝 Commits (1)

  • 0263e43 fix(collection): Do not lock newly created collections

📊 Changes

2 files changed (+1 additions, -1 deletions)

View changed files

📝 CONTRIBUTORS.md (+1 -0)
📝 Emby.Server.Implementations/Library/Validators/CollectionPostScanTask.cs (+0 -1)

📄 Description

From discussion in #14237 :

Fixes #12862 by not locking newly created collections. Once collections are locked, the remote metadata providers are no longer run, which leads to collection information (metadata as well as thumbnails) not being collected since TmdB is a RemoteMetadataProvider.

Existing collections need to be deleted manually after this fix has been merged / shipped.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/jellyfin/jellyfin/pull/14259 **Author:** [@darioackermann](https://github.com/darioackermann) **Created:** 6/9/2025 **Status:** ✅ Merged **Merged:** 6/10/2025 **Merged by:** [@crobibero](https://github.com/crobibero) **Base:** `master` ← **Head:** `dac/fix-collection-locking` --- ### 📝 Commits (1) - [`0263e43`](https://github.com/jellyfin/jellyfin/commit/0263e435eaf84fd8bbcc5879576d1ecc5809bab0) fix(collection): Do not lock newly created collections ### 📊 Changes **2 files changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `CONTRIBUTORS.md` (+1 -0) 📝 `Emby.Server.Implementations/Library/Validators/CollectionPostScanTask.cs` (+0 -1) </details> ### 📄 Description From discussion in #14237 : Fixes #12862 by not locking newly created collections. Once collections are locked, the remote metadata providers are no longer run, which leads to collection information (metadata as well as thumbnails) not being collected since TmdB is a RemoteMetadataProvider. Existing collections need to be deleted manually after this fix has been merged / shipped. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
OVERLORD added the pull-request label 2026-02-07 07:21:11 +03:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
EFjellyfin.db
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
enhancement
feature
future
github-actions
good first issue
hdr
help wanted
invalid
investigation
librarydb
live-tv
lyrics
media playback
music
needs testing
nuget
performance
platform
pull-request
Mirrored from GitHub Pull Request
 question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#13911
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?