[Feature] Say so when a sidecar is skipped, instead of only logging it #564

Closed
opened 2026-07-22 15:10:01 +00:00 by brenno · 0 comments
Owner

Since #560 the four deck sidecars (.ink.json, .user-notes.json, .miauw.json, .seal.json) are read behind a 16 MiB cap. Above it the layer is skipped and the write path leaves the file untouched, so nothing is destroyed — but the user is told nothing. Their ink simply is not there, and the only trace is a line in the log.

That is the right trade for safety and the wrong one for the person looking at their deck. It came out of the guardian review on #560 and was deliberately not folded into that change: making it visible needs its own warning channel, and the existing one is ChartDataWarning, which would show the wrong sentence.

Cost: a warning channel from openDeckDetailed alongside the chart-data one, plus one l10n string × 31 languages.

Reachability, honestly: 16 MiB of ink is hours of continuous annotation, so this is not a common case. It is filed because "the user loses work silently" should not depend on how unlikely we think it is.

Since #560 the four deck sidecars (`.ink.json`, `.user-notes.json`, `.miauw.json`, `.seal.json`) are read behind a 16 MiB cap. Above it the layer is skipped and the write path leaves the file untouched, so nothing is destroyed — but the user is told nothing. Their ink simply is not there, and the only trace is a line in the log. That is the right trade for safety and the wrong one for the person looking at their deck. It came out of the guardian review on #560 and was deliberately not folded into that change: making it visible needs its own warning channel, and the existing one is `ChartDataWarning`, which would show the wrong sentence. Cost: a warning channel from `openDeckDetailed` alongside the chart-data one, plus one l10n string × 31 languages. Reachability, honestly: 16 MiB of ink is hours of continuous annotation, so this is not a common case. It is filed because "the user loses work silently" should not depend on how unlikely we think it is.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
LibreKAT/Ocideck#564
No description provided.