aboutsummaryrefslogtreecommitdiff
path: root/Jellyfin.Server.Implementations/FullSystemBackup/BackupService.cs
diff options
context:
space:
mode:
authorCody Robibero <cody@robibe.ro>2026-07-20 20:15:05 -0400
committerGitHub <noreply@github.com>2026-07-20 20:15:05 -0400
commit0d629591ed8b491e6e3560f72b12d737e4f3922f (patch)
tree0c4e0c80d167b06ff97860ea86de1489cadc1295 /Jellyfin.Server.Implementations/FullSystemBackup/BackupService.cs
parent663a873e07b436cd99fa7b00efa2bcd68e11fb23 (diff)
Remove comments about JSON error handling
Removed comments explaining error handling for malformed JSON during backup.
Diffstat (limited to 'Jellyfin.Server.Implementations/FullSystemBackup/BackupService.cs')
-rw-r--r--Jellyfin.Server.Implementations/FullSystemBackup/BackupService.cs3
1 files changed, 0 insertions, 3 deletions
diff --git a/Jellyfin.Server.Implementations/FullSystemBackup/BackupService.cs b/Jellyfin.Server.Implementations/FullSystemBackup/BackupService.cs
index 765f8bfb73..7c10a5dc77 100644
--- a/Jellyfin.Server.Implementations/FullSystemBackup/BackupService.cs
+++ b/Jellyfin.Server.Implementations/FullSystemBackup/BackupService.cs
@@ -364,9 +364,6 @@ public class BackupService : IBackupService
{
while (true)
{
- // Reading the next row can itself throw, e.g. when a column contains malformed
- // JSON (see https://github.com/jellyfin/jellyfin/issues/17216). Catch that here so a single
- // corrupt row is skipped, logged for manual follow-up, and does not abort the whole backup.
bool hasNext;
try
{