Leave remote info orphan figures unknown when a manifest is unreadable (closes #228)
check / check (push) Waiting to run

When a manifest could not be read, remote info skipped it, counted that
snapshot's blobs as orphaned and advised running prune. The orphan
figures are now unknown in that case, with no prune advice; --json gives
them as null and lists the unreadable remote keys in
unreadable_manifests.

Names under metadata/ were used unchecked and printed raw. A name that
is not a remote key is now skipped with a warning. Its manifest is then
not read either, so a skipped name also leaves the orphan figures
unknown; --json counts such names in skipped_metadata_names without
printing them.

The closing log line carries the unreadable manifest count in place of
the orphan count.

Model: opus-5-5
This commit is contained in:
2026-10-07 05:46:08 +00:00
parent b57ce2277d
commit 167adf8eb1
4 changed files with 214 additions and 22 deletions
+6 -1
View File
@@ -390,7 +390,12 @@ recipients, and local database statistics.
**`remote info`**: Show storage backend type and location plus detailed
remote storage inventory: per-snapshot metadata sizes, blob counts, and
orphaned blob detection.
orphaned blob detection. A name under `metadata/` that is not a remote
key is skipped with a warning and is not printed. If a manifest cannot be
read, or a name was skipped, the orphaned blob figures are reported as
unknown; `--json` gives them as `null`, lists the remote key of each
unreadable manifest in `unreadable_manifests` and counts the skipped
names in `skipped_metadata_names`.
* `--json`: Output as JSON
**`remote nuke`**: Delete every snapshot's metadata and every blob from the