Nectenda/nectenda

Watch

Fork 0

NEC-110: Warn when a note too large to sync (over 16 MiB) enters a shared folder #172

Merged

nectenda-agent merged 2 commits from worktree-nec-110-warn-when-a-note-too-large-to-sync-over into main

2026-09-25 16:56:42 +01:00

nectenda-agent commented

2026-09-25 16:50:37 +01:00

Collaborator

Task: NEC-110 — https://projectron.nerchure.com/tasks/110

A note too large to sync (within 4 KiB of the 16 MiB push limit, or over it) is now named in a notice when it is connected to a shared folder or modified there, once per note across launches and renames, and listed under 'Files that will not sync' in settings while it stays that large (SAFE-A12). Before, SAFE-A11's error appeared only after a push had been tried, on the icon of a note nobody might open. The check reads a size and never stops or delays the connect.

Spec: docs/changes/NEC-110-oversized-note-warning/spec.md

Changelog

Nectenda now warns you when a note in a shared folder is too large to sync (over 16 MiB), and lists such notes in its settings.

Task: NEC-110 — https://projectron.nerchure.com/tasks/110 A note too large to sync (within 4 KiB of the 16 MiB push limit, or over it) is now named in a notice when it is connected to a shared folder or modified there, once per note across launches and renames, and listed under 'Files that will not sync' in settings while it stays that large (SAFE-A12). Before, SAFE-A11's error appeared only after a push had been tried, on the icon of a note nobody might open. The check reads a size and never stops or delays the connect. Spec: `docs/changes/NEC-110-oversized-note-warning/spec.md` ## Changelog Nectenda now warns you when a note in a shared folder is too large to sync (over 16 MiB), and lists such notes in its settings.

nectenda-agent added the

area:plugin

label

2026-09-25 16:50:37 +01:00

nectenda-agent added 2 commits

2026-09-25 16:50:37 +01:00

Name a note too large to sync when it arrives, and list it in settings c6bbd54c7b

A note over the push limit was held back with an error on its icon
(SAFE-A11), but only once a push had been tried and only on a note someone
was looking at. Now connecting or modifying a note within 4 KiB of the
limit names it in one notice per batch, once per note across launches,
and settings lists it under "Files that will not sync" while it stays
that large. The check reads a size and never stops the connect (SAFE-A12).

Task: NEC-110

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CzyXZ1FfBnWFcANDBnUhvD

One notice per folder scan, and a large note's record follows a rename

Release note / release-note (pull_request) Successful in 13s

Details

CI / build (pull_request) Successful in 5m7s

Details

CI / e2e (pull_request) Successful in 5m25s

Details

CI / promote (pull_request) Has been skipped

Details

CI / e2e (push) Successful in 5m28s

Details

CI / build (push) Successful in 5m34s

Details

CI / promote (push) Successful in 33s

Details

e35e3fcf6c

Review findings on the first commit:

- The notice window was fixed from the first large note, so a scan of a
  folder bigger than about 25 notes gave several notices. Every size check
  now restarts it while a warning waits, capped at 30 s, so a scan gives
  one notice once it goes quiet.
- A rename within a folder announced the same note again and left a
  record at the old name that would silence a new note created there. A
  rename is now one call, ContentSync.moveFile, which moves the record;
  a delete or move out drops it.
- The settings list redraws when a listed note's size or existence
  changes, not only when the record does, and the docs say it is drawn
  with the account section rather than while sync is stopped.
- The unmapped-folder prune moved into OversizedNotes so its test runs
  the code main.ts calls, and a doc comment is back above its function.

Task: NEC-110

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CzyXZ1FfBnWFcANDBnUhvD

nectenda-agent merged commit e35e3fcf6c into main

2026-09-25 16:56:42 +01:00

No reviewers

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

Nectenda/nectenda!172

No description provided.

Rows
Columns