jellyfin/src/Jellyfin.Database/Jellyfin.Database.Implementations/Locking, branch v12.0-rc5Unnamed repository; edit this file 'description' to name the repository.
https://git.b0n.dev/jellyfin/atom?h=v12.0-rc52026-08-08T01:43:40ZMerge pull request #17560 from IDisposable/chore/pessimistic-reality-check2026-08-08T01:43:40ZCody Robiberocody@robibe.ro2026-08-08T01:43:40Zurn:sha1:70ffd25b505fff4423d7aab5386d46e327713708
Add warning that PessimisticLockBehavior is unsafeAdd warning that PessimisticLockBehavior is unsafe2026-08-06T05:52:34ZMarc BrooksIDisposable@gmail.com2026-08-06T05:52:34Zurn:sha1:dd81e52f818295a3ef12880f2be8f24c8c1269c0
Since it uses ReaderWriterLockSlim, it gets tripped up if the transaction
is continued across an await boundary on a different thread.
Fix captured (and discarded) Execute exceptions2026-08-06T05:44:51ZMarc BrooksIDisposable@gmail.com2026-08-06T05:44:51Zurn:sha1:868ad089f814740e70939be7ce821a8220c3b4ff
Using ExecuteAndCapture (and the async version) requires something to manage the captured exception, which we don't do. Errors would be silently dropped and the writes/deletes treated as if they succeeded.
Update to .NET 10.02026-01-14T17:55:47ZBond_009bond.009@outlook.com2025-11-11T16:41:46Zurn:sha1:9e480f6efb4bc0e1f0d1323ed7ed5a7208fded99Backport pull request #15328 from jellyfin/release-10.11.z2025-11-03T02:58:46Zevanreichard30810613+evanreichard@users.noreply.github.com2025-11-03T02:58:46Zurn:sha1:a7d039b7c63b0ea9c5bc69898baa1e69d9396908
fix: in optimistic locking, key off table is locked
Original-merge: b5f0199a25cc221ff86d112ed6968a5352277e32
Merged-by: crobibero <cody@robibe.ro>
Backported-by: Joshua M. Boniface <joshua@boniface.me>
Improve optimistic locking behavior (#14779)2025-09-12T19:57:40ZJPVensongithub@jpb.email2025-09-12T19:57:40Zurn:sha1:f0e60a7ff332601b4cc955969c09bdf6f1dd0118Add multiple options for internal locking (#14047)2025-06-03T21:15:22ZJPVensongithub@jpb.email2025-06-03T21:15:22Zurn:sha1:a1d72deba2cb22006af5e286cc3bb23203ec727f