From f8f9ffdf2b51ea234691df879e1cb72ab9c1d05d Mon Sep 17 00:00:00 2001 From: kisfenyo Date: Tue, 1 Sep 2026 06:07:52 +0200 Subject: [PATCH] STATUS: R-414 is the morning's first item - the new nightly check cannot run on demo-felhom --- STATUS.md | 31 +++++++++++++++++++++++-------- 1 file changed, 23 insertions(+), 8 deletions(-) diff --git a/STATUS.md b/STATUS.md index 0f01c396..b94d6af0 100644 --- a/STATUS.md +++ b/STATUS.md @@ -1,8 +1,8 @@ # STATUS — what works, what's broken, what's next -**Updated 2026-08-31 (fourth pass) — the box now checks, every night, that one app's remote -backup still has that app's data in it. It caught a deliberately emptied backup on the first try. -One thing is waiting on you: a golden carrying 0.231.0.** +**Updated 2026-09-01 — I ran the week's six releases against each other overnight. Three things +broke, none of them where I expected. The worst: the backup-content check I shipped yesterday +CANNOT RUN AT ALL on a machine set up like `demo-felhom`, and it fails silently every night.** **Earlier 2026-08-31 — I measured whether the box could test its own remote restore without you, then built the narrow version you picked. The measurement is why it is 3 seconds a night and @@ -18,18 +18,33 @@ not an evening's work.** *This section is allowed to be longer than one screen, and each item says what happens if you do nothing.* -1. **A golden carrying 0.231.0 is owed.** Golden **0.230.0** is baked, vouched and on both +1. **The new nightly backup check does not work on `demo-felhom`** (R-414). It ran for the first + time on its own last night and could not start: that machine has no registered data drive, so + there is nowhere to unpack a backup to look at it. It will fail the same way every night, and + the only trace is one line in a log — the hub cannot tell it apart from a machine that never + had the feature. **Your backups there are fine** — the backup itself ran normally. It is the + CHECK that cannot run. **If you do nothing:** that machine, and any like it, silently never + gets the check. I have not changed anything; the fix is a small decision about where it should + unpack to, and it is yours. + +2. **A golden carrying 0.231.0 is owed.** Golden **0.230.0** is baked, vouched and on both machines. **0.231.0 is the build with the new nightly backup-content check**, and it is on `demo-hp` only. **If you do nothing:** the check stays on one machine; a newly installed box does not get it, and neither does `demo-felhom`. Nothing breaks — this adds a check, it does not fix a defect. Baking and vouching 0.231.0 and raising the floor closes it, the same three-field change as before. -2. **Nothing else about this release.** Everything in 0.231.0 ships in the controller image plus +3. **Whether to keep the test app `bentopdf` on `demo-hp`.** I deployed it last night because it + is the ONLY app of our 53 with neither a database nor stored files — which makes it the only + way to prove the new check does not cry wolf on an app that legitimately has nothing. It + passed silently, which is what we needed to see. **My pick: keep it**, as a permanent control. + **If you do nothing:** it stays, using almost no space. Say the word and I remove it. + +4. **Nothing else about this release.** Everything in 0.231.0 ships in the controller image plus two register lines in the hub (already live). No customer action, no data migration, no credential change. -3. **Whether a documents-only push should still be checked for a missing golden** (R-404). We have now +5. **Whether a documents-only push should still be checked for a missing golden** (R-404). We have now skipped that check **eight times**, each time for a written reason: it runs on every push to the website/documentation repository, including pushes that change nothing a machine installs. **A guard we correctly skip eight times is teaching us to skip it.** @@ -41,11 +56,11 @@ nothing.* **If you do nothing:** nothing breaks, the skipping stays routine, and the count keeps rising. I have NOT changed it; this is yours to decide and mine to build. -4. **Whether to change the hub password** (R-350). I printed it into my own session log on 20 August. +6. **Whether to change the hub password** (R-350). I printed it into my own session log on 20 August. Not in git, not in any saved file — in the log on this machine. **If you do nothing:** it stays as it is, at the risk you accept by leaving it. I can change it without ever showing you the new one. -5. **`demo-hp`'s network setup does not match our own notes** (R-338) — the machine works, the page is +7. **`demo-hp`'s network setup does not match our own notes** (R-338) — the machine works, the page is wrong, or the other way round. **If you do nothing:** the page keeps misleading the next session, as it misled one by an hour.