diff options
| author | zerafachris <christopher.zerafa@blocklabs.io> | 2026-07-18 16:47:23 +0200 |
|---|---|---|
| committer | zerafachris <christopher.zerafa@blocklabs.io> | 2026-07-18 16:47:23 +0200 |
| commit | 663a873e07b436cd99fa7b00efa2bcd68e11fb23 (patch) | |
| tree | 2f94fef9e0a868e6b517a2985de4e9f569526698 /Emby.Server.Implementations/Localization/Core/ca.json | |
| parent | d7727224c2f5024c9981bc70a274826beb7f1cdf (diff) | |
fix: log corrupt KeyframeData row read failures as errors, not warnings
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.
Diffstat (limited to 'Emby.Server.Implementations/Localization/Core/ca.json')
0 files changed, 0 insertions, 0 deletions