Files
felhom.eu/documentation/audits/update-night-2026-09-21/15-r606-hold-sentence-on-the-english-page.txt
T
admin 9c69b3ff07
gates / gates (push) Successful in 27s
Update night: Phases 2-4 evidence — both engines, the unattended HOLD, and five new findings
Evidence off the machine at the end of the phases that produced it (R-320). Teardown follows.

PHASE 2 — the two database engines, through the REAL Update button:
- MariaDB 11.6 -> 12.3 on nextcloud: PROVEN, and pressed through the button for the first time.
  All four SPIKE-r459 observables: the datadir's own record moved 11.6.2 -> 12.3.3; the engine
  itself says "already upgraded ... no need to run mariadb-upgrade again"; the entrypoint says
  "Major version upgrade detected ... Check required!" and then STARTED and FINISHED it (not the
  `skipped due to $MARIADB_AUTO_UPGRADE` line R-459 feared); and the engine took its own
  pre-upgrade backup, 631 905 B. The seeded Nextcloud account read back.
- PostgreSQL 16 -> 17 on docmost: FAILED exactly as R-463 predicted and nobody had measured.
  5.1 s to held; the pin named 17 while nothing ran; the restore brought it back in 29.1 s.
  The engine's REFUSAL LINE was destroyed by failAndHold before any probe could read it, so it
  was REPRODUCED INDEPENDENTLY with a control on every step (R-320).

PHASE 3 — the bad days. B1 produced THE UNATTENDED HOLD, which this project has never had: the
caller pressed once with nobody watching, the app held after 312.9 s, and passes 2 and 3 pressed
nothing. B2 put the pin back on a pull failure in 1.0 s. B3 refused `busy` six times. B4 showed
there is NO single-flight — 5 of 5 updates ran at once and all ended honest. B5 cut the power in
`backing-up` and the box recovered itself and said so. B7 refused under the 2 GB floor. B9 found
R-458's risk narrower than the row states.

PHASE 4 — every badge on the box is TRUE, and the held app answers all four of Q4's questions.

FINDINGS, five new and three corrections to existing rows. The one that matters: R-618 is P1 —
two templates name a health probe the app does not answer, and because the guarded update waits
on that same probe, a SUCCESSFUL update ends by STOPPING a working app. Measured: tandoor served
HTTP 200 on the new version at four samples across five minutes and was then stopped.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
2026-09-21 22:13:57 +02:00

35 lines
2.2 KiB
Plaintext

R-606 CONFIRMED ON THE HOLD SENTENCE — 2026-09-21, guest 9202, controller v0.261.0
==================================================================================
R-606 was found on the INTERRUPTED sentence. This is the same defect on the HOLD sentence, which
R-606's own text ranks highest because it is "a PROMISE ABOUT WHETHER THE CUSTOMER'S FILES COME
BACK". Read off /apps/adventurelog?lang=en while the app was held.
EVERYTHING AROUND IT IS CORRECTLY ENGLISH — positive control:
"Launcher Dashboard Apps Storage Drives Network storage Backup Overview Remote backup"
"An installed app is not running: AdventureLog (stopped) System monitor ->"
"An installed app is not running: Tandoor Recipes (stopped) System monitor ->"
"The hub connection is off - central monitoring is not running"
"AdventureLog Stopped Update available - today Open Log Export Settings"
"Move to another storage You can move this app's data to another connected storage."
THE TWO SENTENCES THAT MATTER ARE HUNGARIAN — on the English page, verbatim:
"A(z) adventurelog frissitese 2026-09-21 20:53-kor nem sikerult, es az alkalmazas nem indult el
az uj verzioval."
"Visszaallithato a Mentesek oldalon ebbol a biztonsagi mentesbol: sajat meghajto, 2026-09-21
20:47 - ez a masolat a beallitasokat, az adatbazist es az adatkoteteket tartalmazza."
(quoted here with ASCII fragments; the live page carries the accents - see
apps/adventurelog/held-page-en.html)
So an English household is told, in English, that their app is stopped and that an update is
available - and told in HUNGARIAN what actually happened, which copy can bring their data back,
when it was taken, and WHAT IS INSIDE IT.
NEGATIVE CONTROL: the Hungarian page carries the same two sentences and the chrome in Hungarian,
so the sentences are not "missing a translation" - they are not translatable at all, because
`Stack.UpdateError` and the hold text are finished STRINGS rather than keys (R-606's mechanism).
ONE MORE THING THIS READING SETTLES, and it is for `09` Q4: the box DOES surface a held app
everywhere, not only on its own page. The banner "An installed app is not running: AdventureLog
(stopped)" appeared at the TOP OF EVERY authenticated page, for both held apps at once.