3.6 KiB
REPORT — v0.347.0 released as the global floor; D62 built and proven; R-1256's last two branches proven live (2026-10-29, attended)
Plain words first. The controller 0.347.0 is the floor for every box since 10:31 CET. It carries the night's restore edges, the escrow wait, the host's OOM count and the 404 fix, plus D62: a restore copy nobody needs stays 30 days, and the household sees it in the kept-copies list and can delete it with „Törlés most". D63 held: the two restore branches that had only tests were proven live on Tester 1, so nothing was reverted.
Commits
| Commit | CI (run id / #) | What |
|---|---|---|
e3fce09 |
2486 / #537 green | D62 — restoreCopyUnusedAge 30 days; backup.RestoreCopies / DeleteRestoreCopy (check + removal under m.mu, path guard); the list rows and the typed-name form (POST /backup/restore-copy/delete, JSON 200/400/404/409/500); restore_copy_deleted event. D63 — faultPoint (test builds only, -tags faultinject). Tests TestD62_*, TestD63_*, each seen failing by a mutation. |
fd75c7c |
2491 / #538 green | the v0.347.0 CHANGELOG heading — the release build's commit. |
Release
- rc.1 (
e3fce09, digestb6640c0a…) on scratch 9202: walk green. - 0.347.0 (
sha256:c79b06e6…, fromfd75c7c): per-box floors for Tester 1, demo-hp, demo-felhom at 09:57 CET — all three moved within a minute; walk green on all three (controller healthy, every container up, 0 refusals, 0 errors, login and file manager 200, https-only OK); one local restore on Tester 1 (2/2 volumes, the app ran, no hold); the OOM line (oneapp_oom, one mail); global floor 10:31 CET, MinAgent 0.158.1, read back from the hub page and its log. - The release image carries no fault switch (
grep -c "FAULT INJECTED"= 0; 2 on the test image).
Live proofs (Tester 1; felhom.eu documentation/audits/d63-2026-10-29/)
- H4 (test build): the snapshot held 3.8.1, the app ran the true 3.8.0; the fault failed the definition write after the compose was written; „the live definition is written back before the start", then the start; the app ran 3.8.0, no hold, both seeded events read back.
- H5's failed stop (test build): a busy volume was not written into; the put-back's stop failed; nothing was put back, the copy stayed, the app was held with the D20 sentence; the held copy's „Törlés most" was off with its reason.
- D62 (test build, then the release build with hub 0.175.0): the copy listed with its date and „automatikusan
törlődik"; a wrong name 400; the right name 200; gone; the hub stored
restore_copy_deleted.
Teardown
Tester 1: throwaway Radicale and Gokapi removed through the product; the 21 empty anonymous volumes this session's backup presses left (R-1267's PrivateBin class) removed by name — 268 volumes, as before; controller 0.347.0 (the release). Radicale's restore hold record stays — clearing it is the operator's. Scratch 9202: controller 0.347.0 (from rc.1), 359 volumes as before. Hub: nothing provisioned.
Rows
Filed: felhom.eu R-1340 (the mixed-hold operator mail tells the option-C story for any cause), R-1341 (the OOM WARN every 30 s). Closed by this release: R-1256, R-528 (with the agent).
After the release — R-1342 (fixed on main 652a690, NOT released)
At 10:39 CET Tester 1 mailed the operator a false „Gokapi did not start … the copy is kept": the D62 live test had deleted the copy during the 30-minute stable-start watch and then removed the app. Now the watched copy reads „checking" and is not deletable, and a removal ends the watch quietly. Tests red first; rides the next controller release.