Skip to content

armgit / Pulse

Public Imported from GitHub
0

Real-time monitoring dashboard for Proxmox VE, PBS, Docker, Kubernetes, TrueNAS and vSphere. Self-hosted, with alerts for failed backups, full disks, unhealthy containers and offline nodes.

Compose PBS accepted-listing repair with current backup inspection

pulse-triage[bot]801b16d87daa
diff --cc docs/release-control/v6/internal/subsystems/storage-recovery.md
index b1077e6cbd,85b762f480..a6b6fbb616
--- a/docs/release-control/v6/internal/subsystems/storage-recovery.md
+++ b/docs/release-control/v6/internal/subsystems/storage-recovery.md
@@@ -21,30 -21,26 +21,50 @@@
## Purpose
+### Unknown restore-point sizes stay unknown across inspection and sorting
+
+Raw inventory retains the provider's reported size. The recovery view admits
+only positive finite bytes for PBS snapshots, PVE backup files and guest
+snapshots; a missing or zero size is unavailable evidence, not a measured
+zero-byte point. Size sorting keeps those unknowns after known values in both
+directions. Existing completed-point counts, verification, retention, protection,
+known-volume chart semantics, identities, filters and requests do not change.
+
+The By date row and its open detail explicitly say **Unknown size**, rather than
+suggesting no size or hiding the field. The detail explains that unknown does
+not mean an empty point. Coverage uses the same wording and explains its limit;
+when the size column is hidden, each disclosed point keeps its size beside its
+source. Ordinary polling updates the same inspected point and focus without
+requiring a new request or dismissing unavailable data as zero.
+
+Normal-suite `backupSizeEvidence.test.tsx` consumes parsed raw PVE/PBS inventory
+and covers zero/missing/one-byte reports for all three sources, both sort
+directions, desktop/phone disclosure and same-point polling. Existing activity
+and inventory suites preserve chart/read semantics. Browser proof exercises
+these raw responses through the actual consuming Backups surface at desktop and
+narrow widths, including unknown/known transitions and inspected pixels. This
+is truthful recovery evidence, not a restored guest or an installed backup test.
+
+ ### PBS collection expiry preserves accepted scopes without inventing safety
+
+ PBS publishes namespace and snapshot listings accepted before a later child
+ budget expires. Unread datastores/namespaces and failed or queued snapshot groups
+ retain only existing raw history and cache times. Late responses are unread;
+ accepted empty scopes remove only their own raw inventory. Partial enumeration
+ does not reconcile durable absence, renew unread evidence, or claim protection.
+ Unknown live-writer visibility keeps incomplete artifacts non-successful, never
+ invents a completion. Explicit cancellation or an ended runtime/client binding
+ still prevents publication, even after dropping a spent child deadline.
+
+ `pbs_backup_budget_test.go` and the registered protection-observation entry point
+ exercise actual PBS HTTP collection through live state, mapper, durable ingest
+ and posture for VM/CT, warm/cold state, every expiry phase and ordinary recovery.
+ Lifecycle tests cover the background owner and same-name client replacement.
+ Desktop/narrow browser proof consumes those emitted inventory/posture frames
+ through existing Backups polling and disclosures; dates, partial protection and
+ independent unread records must remain legible. No new API, auth, policy,
+ retention, guest operation, release or installed-recovery claim is implied.
+
### Selected PBS datastore remains inspectable without hover
The existing PBS row disclosure is named by backup reader and datastore, rather