jellyfin/Jellyfin.Server.Implementations/FullSystemBackup/BackupService.cs, branch v12.0-rc3Unnamed repository; edit this file 'description' to name the repository.
https://git.b0n.dev/jellyfin/atom?h=v12.0-rc32026-07-21T00:15:05ZRemove comments about JSON error handling2026-07-21T00:15:05ZCody Robiberocody@robibe.ro2026-07-21T00:15:05Zurn:sha1:0d629591ed8b491e6e3560f72b12d737e4f3922f
Removed comments explaining error handling for malformed JSON during backup.fix: log corrupt KeyframeData row read failures as errors, not warnings2026-07-18T14:47:23Zzerafachrischristopher.zerafa@blocklabs.io2026-07-18T14:47:23Zurn:sha1:663a873e07b436cd99fa7b00efa2bcd68e11fb23
Per review feedback from cvium: failing to read/backup an entity due to
corrupt underlying data is a significant event that should be surfaced
as an error, not silently downgraded to a warning.
Skip corrupt KeyframeData rows during full system backup2026-07-17T14:44:25Zzerafachrischristopher.zerafa@blocklabs.io2026-07-17T14:44:25Zurn:sha1:d7727224c2f5024c9981bc70a274826beb7f1cdf
A single row with malformed KeyframeTicks JSON (e.g. a truncated array
from an interrupted write) currently aborts the entire backup, because
the try/catch in BackupService.CreateBackupAsync only wraps
serialization of an already-materialized entity, not the enumeration
itself. EF Core throws JsonReaderException from MoveNextAsync() while
materializing the corrupt row, which propagates past that catch block.
Switch to manual enumerator iteration so MoveNextAsync() failures can
be caught per-row, logged as a warning identifying the affected table,
and skipped, allowing the remaining rows and the rest of the backup to
complete.
Fixes #17216
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Skip backups whens can is running2026-06-26T05:34:19ZShadowghostGhost_of_Stone@web.de2026-06-26T05:34:19Zurn:sha1:fa07a3abe89b6e0eb96a9f8d8a3eb57dea20ca2aBackport pull request #16425 from jellyfin/release-10.11.z2026-03-30T18:08:04Ztheguymadmax171496228+theguymadmax@users.noreply.github.com2026-03-30T18:08:04Zurn:sha1:7825fa4e43f1970aa46d5ee0e986dee019bf4dd2
Fix restore backup metadata location
Original-merge: 0f1732e5f5444cd6876dec816b5ff5822a93862b
Merged-by: joshuaboniface <joshua@boniface.me>
Backported-by: Bond_009 <bond.009@outlook.com>
Update to .NET 10.02026-01-14T17:55:47ZBond_009bond.009@outlook.com2025-11-11T16:41:46Zurn:sha1:9e480f6efb4bc0e1f0d1323ed7ed5a7208fded99Backport pull request #15196 from jellyfin/release-10.11.z2025-10-27T19:43:25Zcrobiberocody@robibe.ro2025-10-27T19:43:25Zurn:sha1:0f21222a0c873b9e3e258ec6c3ed32278b41614f
Skip directory entry when restoring from backup
Original-merge: 0e4031ae52b2ca3a19e22bfc6ab9c9af88944bd8
Merged-by: crobibero <cody@robibe.ro>
Backported-by: Bond_009 <bond.009@outlook.com>
Backport pull request #15170 from jellyfin/release-10.11.z2025-10-27T19:43:20Zcrobiberocody@robibe.ro2025-10-27T19:43:20Zurn:sha1:ed6cb30762dbeb018209e19a8896059e4f906c1b
Clean up BackupService
Original-merge: ac3fa3c376a47c099e14d4b940832c39e2249aee
Merged-by: crobibero <cody@robibe.ro>
Backported-by: Bond_009 <bond.009@outlook.com>
Various cleanups (#14785)2025-09-12T19:58:23ZBond-009bond.009@outlook.com2025-09-12T19:58:23Zurn:sha1:8776a447d1c2fc553d24bc1162f27017f84e80bbClean up and fix backup/restore (#14489)2025-07-21T02:01:13ZCody Robiberocody@robibe.ro2025-07-21T02:01:13Zurn:sha1:36c90ce2ce361dfdc165a1deda3434e66d28ef52