1 Commits
Author SHA1 Message Date
sneak 857feeeddb Record the defect-hunt fixes in TODO.md Completed Steps (closes #334)
check / check (push) Canceled after 0s
Adds a Completed Steps entry, newest first, for every issue from the
defect hunt (#288) that a merged
fix closed and that had none: the hunt's own issues, those filed while
fixing them, and the owner's ruling on
#239. Each entry was checked
against the code on `next`. Next Step now says the hunt's fixes have
landed.

Judgement call: #332, closed as
covered by the fix for #296, is
named in that entry rather than given its own.
Judgement call: #351, a Docker
build fix filed while gating these fixes, gets an entry.

Model: opus-5-5
2026-10-14 06:10:15 +00:00
+12 -11
View File
@@ -185,8 +185,8 @@ owner's; a `v*` tag runs the release build in
makes an anchored pattern match at every depth too, and each `/**/`
inside a pattern also matches a single `/`.
- 2026-10-13: Made the size defaults and the `chunk_size` minimum
1000-based
- 2026-10-13: Made the `chunk_size` and `blob_size_limit` defaults and
the `chunk_size` minimum 1000-based
([issue #313](https://git.eeqj.de/sneak/vaultik/issues/313)). They
were 1024-based while the size parser, the docs and `info` use
1000-based units, so `chunk_size: 1MB` was rejected, writing out a
@@ -259,9 +259,10 @@ owner's; a `v*` tag runs the release build in
backup runs
([issue #360](https://git.eeqj.de/sneak/vaultik/issues/360)).
`snapshot list` summed the chunks a snapshot reaches through file
rows that every snapshot shares and that a changed file rewrites, so
backing up a changed file changed every older snapshot's UNCOMPRESSED
SIZE. The backup now stores that total in the `snapshots` table's
rows shared by every snapshot that lists the file and that a changed
file rewrites, so backing up a changed file changed the UNCOMPRESSED
SIZE of every older snapshot that lists that file. The backup now
stores that total in the `snapshots` table's
`uncompressed_chunk_size`, which `snapshot list` reads.
- 2026-10-13: Stopped `snapshot restore --verify` reporting a file that
@@ -333,12 +334,12 @@ owner's; a `v*` tag runs the release build in
- 2026-10-13: Recorded each snapshot's new chunk size when its backup
runs ([issue #311](https://git.eeqj.de/sneak/vaultik/issues/311)).
`snapshot list` worked out NEW CHUNK SIZE from file rows that every
snapshot shares and that a changed file rewrites, so a snapshot whose
change was a modified file showed 0 B and older snapshots' figures
moved after later backups. The backup now stores the size of the
chunks it newly stored in the `snapshots` table's `new_chunk_size`,
which `snapshot list` reads.
`snapshot list` worked out NEW CHUNK SIZE from file rows shared by
every snapshot that lists the file and that a changed file rewrites,
so a snapshot whose change was a modified file showed 0 B and older
snapshots' figures moved after later backups. The backup now stores
the size of the chunks it newly stored in the `snapshots` table's
`new_chunk_size`, which `snapshot list` reads.
- 2026-10-13: Made a backup interrupted during a local index write exit
as interrupted