Skip to content

Noda 1.0.3 — Reliable note-processing retries

Latest

Choose a tag to compare

@Timaga Timaga released this 18 Nov 18:09
864dc1d

Noda 1.0.3

Stable fix release — Windows 10/11 x64 with AVX2.

Fix

A note could remain unprocessed when another note was edited, added or moved to
trash while metadata generation was running. Titles and tags could have finished,
but the final archive validation rejected the outdated snapshot.

The queue now retries the same job against a fresh archive within its existing
attempt and backoff limits (three attempts by default). Strict inventory and
full-file hash checks remain enabled. Deleted notes are not restored, stale links
are not published, and duplicate requests retain the same job identity.

If the archive keeps changing until the attempt limit is reached, the exact
submitted text is saved as an unprocessed note with manual retry available.
Previously saved unprocessed notes can be retried through the queue; installing
this version does not replay them automatically. Other permanent model or
configuration failures retain their previous behavior.

Queue and recovery flow.

Install and update

Download Noda-Setup-1.0.3-x64.exe and SHA256SUMS.txt from this release.
The full source ZIP and VALIDATION.md are provided separately.

  1. Back up project folders and %APPDATA%\Noda.
  2. Save edits and fully exit Noda through its tray menu.
  3. Run Setup and retain the existing installation folder.
  4. Open Noda. Existing unprocessed notes can be retried individually from the queue.

No dependency, queue schema, public response shape or model-selection default is
changed by this fix. Model weights remain outside Setup and Git. There is no
automatic application updater.

Verification and limits

The fix has eight regression cases covering archive deletion/edit/addition,
bounded exhaustion, exact-source preservation, same-job idempotency, in-place
recovery and unchanged handling of other permanent failures. Local isolated suites
passed 756 Python tests and 28 subtests; 658 Node tests. The final commit,
artifact hashes, packaged-source checks and CI evidence are recorded with the
release assets. Tests use synthetic notes and synthetic model responses; they do
not establish broad real-model quality or verify a private user's note outcome.

The Windows executable is unsigned. Exact-binary installation on a clean
machine and installation interruption recovery remain separate checks. Earlier
installer lifecycle evidence applies to the unchanged installer source and does
not replace those checks. Back up data before a downgrade; replacing binaries
alone does not restore previous queue/profile state.

Known dependency issues and
compliance scope remain applicable. Separate
Accelerate/DiskCache/PT2 concerns retain the documented supported-profile
mitigations. This release does not claim upstream fixes, safe untrusted models,
regulatory certification or complete application coverage.

Source commit: 864dc1d4116365092239cf1656777351c0b1adf2. See the attached VALIDATION.md and SHA256SUMS.txt for checks and limitations.