docs(hub v0.108.0): the delivery grain, the cooldown ruling, and gate 11's first subject
gates / gates (push) Successful in 15s
gates / gates (push) Successful in 15s
The alarm ladder gains §6.2 - which events are per-app, per-run, per-tier or coarse, and why the default is coarse. CONTEXT records two rulings: the grain is allow-listed rather than inferred from the payload, with crossdrive_failed as the proof that a payload rule would have been wrong; and a finding recorded only in REPORT.md has a lifetime of one session. R-389 closed and compressed, keeping its rules and naming the commit whose git show returns the full text. R-390 and R-391 left open. REPORT.md is gate 11's first real subject and passes: six observations, two FILED, four NOT-A-FINDING with their reasons. Three of those declarations are things a tidier report would have omitted - the gate's own spec would have passed the item it was built to catch, the burst has no ceiling, and ArgoCD said "successfully rolled out" while still running the old image. STATUS carries forward the one thing outstanding: the controller floor still reads 0.222.0 while the golden reads 0.223.0.
This commit is contained in:
@@ -0,0 +1,118 @@
|
||||
# DRILL — R-389: only the first broken app per hour reached the operator (2026-08-23)
|
||||
|
||||
**Hub v0.107.0 → v0.108.0. No controller release, so no golden and no floor.** Live leg on `demo-hp`
|
||||
(Tier 0) plus the hub. UNATTENDED. Method: the hub's own SQLite records plus the controller log.
|
||||
Guest and hub DB are UTC; the hub pod logs CEST.
|
||||
|
||||
**No halt condition fired.**
|
||||
|
||||
## The pair that says it
|
||||
|
||||
Same box, same shape — two apps down four minutes apart, inside one hour:
|
||||
|
||||
```
|
||||
2026-08-23 09:27:51 sent BookStack <- v0.107.0
|
||||
2026-08-23 09:31:51 suppressed PrivateBin operator cooldown 1h, key=demo-hp:app_start_failed
|
||||
|
||||
2026-08-23 11:56:57 sent OpenGist <- v0.108.0
|
||||
2026-08-23 12:00:57 sent Calibre-Web
|
||||
```
|
||||
|
||||
**2 sent / 0 suppressed**, where the day before the identical shape gave one of each.
|
||||
|
||||
And the keys, from the hub's own suppression rows — it records the key only when it declines:
|
||||
|
||||
```
|
||||
operator cooldown 1h, key=demo-hp:app_start_failed:opengist
|
||||
operator cooldown 1h, key=demo-hp:app_start_failed:calibre-web
|
||||
```
|
||||
|
||||
against v0.107.0's shared `key=demo-hp:app_start_failed`.
|
||||
|
||||
## The fence, and why it is not decoration
|
||||
|
||||
`crossdrive_failed` is severity `error`, reaches the operator leg, and carries `stack_name` — through
|
||||
`CrossDriveDetails`, **a different struct from `AppDetails`**. A rule of the form *"if the details
|
||||
carry a stack_name, split per app"* would have split it and silently undone R-182.
|
||||
|
||||
Proven live: two different apps' `crossdrive_failed`, one minute apart →
|
||||
|
||||
```
|
||||
sent opengist
|
||||
suppressed calibre-web operator cooldown 1h, key=demo-hp:crossdrive_failed
|
||||
```
|
||||
|
||||
**Byte-identical to the derived v0.107.0 key. No app suffix.** That is why `cooldownStackSuffix`
|
||||
takes the event type as well as the details, unlike its two siblings.
|
||||
|
||||
## Part 2 — the burst, measured
|
||||
|
||||
Three apps stopped in one scan (`kimai`, `romm`, `paperless-ngx`, none with a live cooldown — checked
|
||||
first, because a stale one would have halved the count and made the answer look better than it is):
|
||||
|
||||
| | |
|
||||
|---|---|
|
||||
| attempted | **3** |
|
||||
| sent | **3** |
|
||||
| suppressed | **0** |
|
||||
|
||||
**Judgement: per-app is the right grain, and this volume is acceptable.** The reference box has 8
|
||||
deployed apps, so a total outage is 8 mails; the boot grace (90 s), the quiesce grace (180 s) and the
|
||||
per-app edge trigger absorb reboots, backup cycles and persistently-dead apps. **No digest row was
|
||||
filed.** The reopening condition is stated rather than left implicit: it scales linearly with app
|
||||
count and has no ceiling, so a box large enough that a total outage is unreadable is the point at
|
||||
which the answer becomes a digest with a customer message — not a wider cooldown.
|
||||
|
||||
## Part 3 — gate 11, and the spec discrepancy it forced
|
||||
|
||||
The gate refuses a push whose `REPORT.md` carries an observation with neither `FILED: R-NNN` nor
|
||||
`NOT-A-FINDING: <reason>`.
|
||||
|
||||
**The specification said an item may "cite an R-NNN that resolves". That rule would have passed the
|
||||
very item the gate was built to catch.** Yesterday's lost observation reads *"This is R-182's known
|
||||
cooldown-key shape…"* — `R-182` resolves, and it is cited as an **analogy**, not as the row that files
|
||||
it. No parser can tell citation-as-precedent from citation-as-filing by reading prose. The marker is
|
||||
therefore explicit, and the discrepancy is recorded in the gate's docstring rather than quietly
|
||||
resolved. `EDGE 7` in the evidence is that exact case, convicted.
|
||||
|
||||
| Control | Expected | Observed |
|
||||
|---|---|---|
|
||||
| historical: yesterday's real section, verbatim | refuse | **exit 1**, naming both items |
|
||||
| plant an observation with no row | refuse | **exit 1** |
|
||||
| add the row | pass | **exit 0** |
|
||||
| remove the observation | pass quietly | **exit 0** |
|
||||
| `FILED:` a row that does not resolve | refuse | **exit 1** |
|
||||
| `NOT-A-FINDING:` with no reason | refuse | **exit 1** |
|
||||
| both markers on one item | refuse | **exit 1** |
|
||||
| section present, no numbered items | inconclusive | **exit 2**, saying what it could not read |
|
||||
| no `REPORT.md` at all | inconclusive | **exit 2** |
|
||||
| a bare `R-182` mention (the trap) | refuse | **exit 1** |
|
||||
|
||||
## Evidence index (`evidence/`)
|
||||
|
||||
| File | What it shows |
|
||||
|---|---|
|
||||
| `redproof-1-key.txt` | suffix dropped from the key → `1 operator mail(s), want 2`, and the live key shape reproduced |
|
||||
| `redproof-2-allowlist.txt` | allow-list removed → `crossdrive_failed`, `app_deployed`, `app_removed`, `backup_failed` all split per app |
|
||||
| `gate11-01-historical-redproof.txt` | yesterday's actual observations section, refused |
|
||||
| `gate11-02-three-controls.txt` | plant → refuse, file → pass, remove → pass |
|
||||
| `gate11-03-edges.txt` | seven boundaries incl. the R-182 trap |
|
||||
| `live-01`…`live-05` | Scenarios A and B: both sent, then each suppressed under its own key |
|
||||
| `live-06`, `live-07` | Scenario C: crossdrive stays coarse |
|
||||
| `live-08`, `live-09` | the burst, with its pre-check |
|
||||
| `live-10-full-controller-log.txt` | 1803 lines, pulled before the restore |
|
||||
|
||||
## Teardown
|
||||
|
||||
Nothing provisioned. Five apps were stopped across the walk (`opengist`, `calibre-web`, `kimai`,
|
||||
`romm`, `paperless-ngx`) and **all were restarted and confirmed healthy** — 17 containers up. No app
|
||||
was rebuilt, redeployed or restored; the three retained subjects (`docmost`, `bookstack`,
|
||||
`privatebin`) were not touched at all.
|
||||
|
||||
**Hub-side, stated explicitly.** The hub was written this session: deployment to v0.108.0 via the
|
||||
manifest, and **six probe events were POSTed to the live hub** for Scenarios B and C (two
|
||||
`app_start_failed`, two `crossdrive_failed`, plus the two from yesterday's Scenario H that were
|
||||
deliberately left in place). They are inert event rows for `demo-hp` and are named here rather than
|
||||
left to be found. **Every count in this drill is filtered by `created_at >= T0`** precisely so those
|
||||
rows cannot contaminate it. Nothing else: no appliance registered, no customer created, no artifact
|
||||
manifest changed, floor untouched.
|
||||
+16
@@ -0,0 +1,16 @@
|
||||
### HISTORICAL RED-PROOF — yesterday's ACTUAL observations section, verbatim from 2f7c9a6 ###
|
||||
report : ../../../../../tmp/claude-1000/-mnt-5-hdd-felhom-eu-git/3b17bdbd-9113-4908-9b30-15678f2978bc/scratchpad/gate11/REPORT.md
|
||||
section : ## 10. Observations — recorded, not acted on
|
||||
observation items : 2
|
||||
|
||||
OBSERVATIONS GATE FAILED: 2 observation(s) with nothing behind them.
|
||||
|
||||
item 1: **The operator cooldown key carries no app identifier.** PrivateBin's alarm fo…
|
||||
neither `FILED: R-NNN` nor `NOT-A-FINDING: <reason>`
|
||||
|
||||
item 2: Two probe events remain as rows for `demo-hp` from Scenario H — inert, and nam…
|
||||
neither `FILED: R-NNN` nor `NOT-A-FINDING: <reason>`
|
||||
|
||||
An observation that lives only in REPORT.md has a lifetime of ONE SESSION — this file is overwritten every time. That is how the cooldown-grain finding was lost on 2026-08-23 and had to be re-derived the next day.
|
||||
Fix: add `FILED: R-NNN` naming the row you opened for it, or `NOT-A-FINDING: <why this is not worth a row>`. Opening the row is the default; declaring is the exception and needs its reason stated.
|
||||
EXIT=1 (want 1)
|
||||
+25
@@ -0,0 +1,25 @@
|
||||
### CONTROL 1 — an observation with NO row: must REFUSE (1) ###
|
||||
report : ../../../../../tmp/claude-1000/-mnt-5-hdd-felhom-eu-git/3b17bdbd-9113-4908-9b30-15678f2978bc/scratchpad/gate11/c1.md
|
||||
section : ## 9. Observations
|
||||
observation items : 1
|
||||
|
||||
OBSERVATIONS GATE FAILED: 1 observation(s) with nothing behind them.
|
||||
|
||||
item 1: The operator cooldown key carries no app identifier, so only the first app per…
|
||||
neither `FILED: R-NNN` nor `NOT-A-FINDING: <reason>`
|
||||
|
||||
An observation that lives only in REPORT.md has a lifetime of ONE SESSION — this file is overwritten every time. That is how the cooldown-grain finding was lost on 2026-08-23 and had to be re-derived the next day.
|
||||
Fix: add `FILED: R-NNN` naming the row you opened for it, or `NOT-A-FINDING: <why this is not worth a row>`. Opening the row is the default; declaring is the exception and needs its reason stated.
|
||||
EXIT=1
|
||||
|
||||
### CONTROL 2 — add the row: must PASS (0) ###
|
||||
report : ../../../../../tmp/claude-1000/-mnt-5-hdd-felhom-eu-git/3b17bdbd-9113-4908-9b30-15678f2978bc/scratchpad/gate11/c2.md
|
||||
section : ## 9. Observations
|
||||
observation items : 1
|
||||
OK 1. FILED R-389
|
||||
observations gate OK — every observation is either filed or explicitly declared
|
||||
EXIT=0
|
||||
|
||||
### CONTROL 3 — remove the observation entirely: must PASS quietly (0) — Scenario F ###
|
||||
observations gate OK — c3.md has no observations section (nothing to check)
|
||||
EXIT=0
|
||||
@@ -0,0 +1,44 @@
|
||||
### EDGE 1 — NOT-A-FINDING with a reason: PASS (0) ###
|
||||
section : ## Observations
|
||||
observation items : 1
|
||||
OK 1. NOT-A-FINDING
|
||||
observations gate OK — every observation is either filed or explicitly declared
|
||||
EXIT=0
|
||||
|
||||
### EDGE 2 — FILED with a row that does NOT resolve: REFUSE (1) ###
|
||||
`FILED: R-99999` does not resolve — no row for R-99999 in OPEN-ITEMS.md or CLOSED-ITEMS.md
|
||||
|
||||
An observation that lives only in REPORT.md has a lifetime of ONE SESSION — this file is overwritten every time. That is how the cooldown-grain finding was lost on 2026-08-23 and had to be re-derived the next day.
|
||||
Fix: add `FILED: R-NNN` naming the row you opened for it, or `NOT-A-FINDING: <why this is not worth a row>`. Opening the row is the default; declaring is the exception and needs its reason stated.
|
||||
EXIT=1
|
||||
|
||||
### EDGE 3 — NOT-A-FINDING with no reason: REFUSE (1) ###
|
||||
`NOT-A-FINDING:` carries no reason — the reason is the whole point of the marker
|
||||
|
||||
An observation that lives only in REPORT.md has a lifetime of ONE SESSION — this file is overwritten every time. That is how the cooldown-grain finding was lost on 2026-08-23 and had to be re-derived the next day.
|
||||
Fix: add `FILED: R-NNN` naming the row you opened for it, or `NOT-A-FINDING: <why this is not worth a row>`. Opening the row is the default; declaring is the exception and needs its reason stated.
|
||||
EXIT=1
|
||||
|
||||
### EDGE 4 — BOTH markers on one item: REFUSE (1) ###
|
||||
carries BOTH `FILED:` and `NOT-A-FINDING:` — decide which it is
|
||||
|
||||
An observation that lives only in REPORT.md has a lifetime of ONE SESSION — this file is overwritten every time. That is how the cooldown-grain finding was lost on 2026-08-23 and had to be re-derived the next day.
|
||||
Fix: add `FILED: R-NNN` naming the row you opened for it, or `NOT-A-FINDING: <why this is not worth a row>`. Opening the row is the default; declaring is the exception and needs its reason stated.
|
||||
EXIT=1
|
||||
|
||||
### EDGE 5 — section present, NO numbered items: INCONCLUSIVE (2) ###
|
||||
OBSERVATIONS GATE INCONCLUSIVE: found the section '## Observations' but no numbered items under it.
|
||||
Items must be a numbered list (`1.`, `2.` …). If the section is deliberately empty, remove the heading — an empty section reads as coverage while providing none.
|
||||
EXIT=2
|
||||
|
||||
### EDGE 6 — REPORT.md absent: INCONCLUSIVE (2) ###
|
||||
OBSERVATIONS GATE INCONCLUSIVE: no REPORT.md at /tmp/claude-1000/-mnt-5-hdd-felhom-eu-git/3b17bdbd-9113-4908-9b30-15678f2978bc/scratchpad/gate11/does-not-exist.md
|
||||
This gate is registered here because this repo keeps one. If it was removed deliberately, unregister the gate in the runner rather than leaving it unreadable.
|
||||
EXIT=2
|
||||
|
||||
### EDGE 7 — the R-182 TRAP: a bare mention must NOT satisfy the gate (1) ###
|
||||
neither `FILED: R-NNN` nor `NOT-A-FINDING: <reason>`
|
||||
|
||||
An observation that lives only in REPORT.md has a lifetime of ONE SESSION — this file is overwritten every time. That is how the cooldown-grain finding was lost on 2026-08-23 and had to be re-derived the next day.
|
||||
Fix: add `FILED: R-NNN` naming the row you opened for it, or `NOT-A-FINDING: <why this is not worth a row>`. Opening the row is the default; declaring is the exception and needs its reason stated.
|
||||
EXIT=1
|
||||
@@ -0,0 +1,16 @@
|
||||
=== LIVE WALK — pre-state ===
|
||||
hub image: gitea.dooplex.hu/admin/felhom-hub:0.108.0
|
||||
2026-08-23T11:56:06Z
|
||||
controller: gitea.dooplex.hu/admin/felhom-controller:0.223.0 Up 2 hours (healthy)
|
||||
|
||||
bookstack Up 9 hours (healthy)
|
||||
bookstack-db Up 2 hours (healthy)
|
||||
calibre-web Up 9 hours (healthy)
|
||||
docmost Up 6 hours (healthy)
|
||||
docmost-postgres Up 6 hours (healthy)
|
||||
docmost-redis Up 6 hours (healthy)
|
||||
opengist Up 9 hours (healthy)
|
||||
privatebin Up 2 hours (healthy)
|
||||
|
||||
-- T0 for every count below: any notification_log row created at or after this instant --
|
||||
T0=2026-08-23T11:56:06Z
|
||||
+8
@@ -0,0 +1,8 @@
|
||||
=== SCENARIO A — two DIFFERENT apps down inside the hour ===
|
||||
subjects: opengist and calibre-web (single-container, intent running, neither on the
|
||||
do-not-rebuild list). Stopped OUT OF BAND so the controller's own Deploying skip cannot mask it.
|
||||
opengist desired_state: running
|
||||
calibre-web desired_state: running
|
||||
|
||||
APP 1 (opengist) down at: 2026-08-23T11:56:26Z
|
||||
opengist Exited (0) 5 seconds ago
|
||||
+8
@@ -0,0 +1,8 @@
|
||||
-- waiting 4 minutes, then APP 2 — the same gap that produced one mail yesterday --
|
||||
APP 2 (calibre-web) down at: 2026-08-23T12:00:48Z
|
||||
opengist Exited (0) 4 minutes ago
|
||||
calibre-web Exited (0) 5 seconds ago
|
||||
|
||||
-- letting the second alarm land --
|
||||
2026/08/23 11:56:56 notifier.go:234: [INFO] Event pushed: app_start_failed (warning) — Telepített alkalmazás nem fut: OpenGist
|
||||
2026/08/23 12:00:57 notifier.go:234: [INFO] Event pushed: app_start_failed (warning) — Telepített alkalmazás nem fut: Calibre-Web Automated
|
||||
+11
@@ -0,0 +1,11 @@
|
||||
=== SCENARIO A — the hub's notification log, filtered to created_at >= T0 (11:56:06Z) ===
|
||||
(the T0 filter is what keeps yesterday's two inert Scenario H probe rows out of every count)
|
||||
|
||||
status channel message key_or_reason created_at
|
||||
------ -------- -------------------------------------------- ------------- -------------------
|
||||
sent operator Telepített alkalmazás nem fut: OpenGist 2026-08-23 11:56:57
|
||||
sent operator Telepített alkalmazás nem fut: Calibre-Web A 2026-08-23 12:00:57
|
||||
|
||||
-- counts --
|
||||
sent : 2
|
||||
suppressed: 0
|
||||
+8
@@ -0,0 +1,8 @@
|
||||
=== SCENARIO B — the SAME app again inside the hour: one sent, one suppressed ===
|
||||
Posted through the exact endpoint the controller invokes (/api/v1/event), with the controller's
|
||||
own AppDetails payload. The controller's own event is edge-triggered per app, so a down->down
|
||||
cycle is silent by design and cannot re-fire it from the box.
|
||||
|
||||
T_B=2026-08-23T12:02:48Z
|
||||
repeat OpenGist http=200
|
||||
repeat Calibre-Web http=200
|
||||
+15
@@ -0,0 +1,15 @@
|
||||
=== SCENARIOS A + B — every operator row since T0, with the KEY where the hub records it ===
|
||||
status app key_or_reason created_at
|
||||
---------- ---------------------- -------------------------------------------------------------- -------------------
|
||||
sent ut: OpenGist 2026-08-23 11:56:57
|
||||
sent ut: Calibre-Web Automa 2026-08-23 12:00:57
|
||||
suppressed ut: OpenGist operator cooldown 1h, key=demo-hp:app_start_failed:opengist 2026-08-23 12:02:48
|
||||
suppressed ut: Calibre-Web operator cooldown 1h, key=demo-hp:app_start_failed:calibre-web 2026-08-23 12:02:48
|
||||
|
||||
-- THE KEYS, side by side. Yesterday BOTH apps shared key=demo-hp:app_start_failed. --
|
||||
operator cooldown 1h, key=demo-hp:app_start_failed:opengist
|
||||
operator cooldown 1h, key=demo-hp:app_start_failed:calibre-web
|
||||
|
||||
-- counts since T0 --
|
||||
sent : 2
|
||||
suppressed: 2
|
||||
+15
@@ -0,0 +1,15 @@
|
||||
=== SCENARIO C — a backup-family event carrying stack_name must NOT split per app ===
|
||||
subject: crossdrive_failed — severity error, reaches the operator leg, carries stack_name
|
||||
through CrossDriveDetails. Two DIFFERENT apps: if the key had split, both would send.
|
||||
|
||||
HOW THE 'BEFORE' VALUE WAS OBTAINED, two independent ways:
|
||||
(a) derivation from v0.107.0's expression, which is customerID:eventType + tier + run and
|
||||
carries no app term, so for this payload it is exactly 'demo-hp:crossdrive_failed';
|
||||
(b) TestR389_NoOtherEventTypeKeyChanges models that v0.107.0 expression INLINE and compares
|
||||
it against the live one for 12 event types — with a positive control proving the test
|
||||
can see a key change before it reports that none occurred.
|
||||
The live key printed below must equal that.
|
||||
|
||||
T_C=2026-08-23T12:03:44Z
|
||||
crossdrive_failed opengist http=200
|
||||
crossdrive_failed calibre-web http=200
|
||||
+8
@@ -0,0 +1,8 @@
|
||||
-- SCENARIO C result: the operator rows for crossdrive_failed since T_C --
|
||||
status app key_or_reason created_at
|
||||
---------- ---------- --------------------------------------------------- -------------------
|
||||
suppressed alibre-web operator cooldown 1h, key=demo-hp:crossdrive_failed 2026-08-23 12:03:44
|
||||
sent pengist 2026-08-23 12:03:45
|
||||
|
||||
-- the live key, to compare against the derived v0.107.0 value 'demo-hp:crossdrive_failed' --
|
||||
operator cooldown 1h, key=demo-hp:crossdrive_failed
|
||||
@@ -0,0 +1,21 @@
|
||||
-- restoring the two Scenario A/B subjects before the burst --
|
||||
opengist Up 20 seconds (healthy)
|
||||
calibre-web Up 20 seconds (healthy)
|
||||
|
||||
=== PART 2 — THE BURST: three apps down in ONE scan ===
|
||||
subjects: kimai, romm, paperless-ngx — none has alarmed inside the last hour, so no
|
||||
pre-existing cooldown can mask the count. Verified below before stopping them.
|
||||
-- CONTROL: no app_start_failed row for these three in the last hour (a stale cooldown would
|
||||
silently halve the count and the burst would look better than it is) --
|
||||
rows for kimai/romm/paperless since 11:04: 0
|
||||
|
||||
T_BURST=2026-08-23T12:05:03Z
|
||||
2026-08-23T12:05:13Z
|
||||
kimai Exited (0) 9 seconds ago
|
||||
kimai-db Exited (0) 8 seconds ago
|
||||
paperless-postgres Exited (0) 4 seconds ago
|
||||
paperless-redis Exited (0) 4 seconds ago
|
||||
paperless-webserver Exited (0) 4 seconds ago
|
||||
romm Exited (0) 9 seconds ago
|
||||
romm-db Exited (0) 9 seconds ago
|
||||
romm-redis Exited (0) 9 seconds ago
|
||||
+18
@@ -0,0 +1,18 @@
|
||||
-- PART 2 — THE BURST RESULT (T_BURST = 12:05:03Z) --
|
||||
|
||||
controller side, what it SENT:
|
||||
2026/08/23 12:05:26 notifier.go:234: [INFO] Event pushed: app_start_failed (warning) — Telepített alkalmazás nem fut: Kimai
|
||||
2026/08/23 12:05:26 notifier.go:234: [INFO] Event pushed: app_start_failed (warning) — Telepített alkalmazás nem fut: RomM
|
||||
2026/08/23 12:05:26 notifier.go:234: [INFO] Event pushed: app_start_failed (warning) — Telepített alkalmazás nem fut: Paperless-ngx
|
||||
|
||||
hub side, the operator rows:
|
||||
status app key_or_reason created_at
|
||||
------ ----------------- ------------- -------------------
|
||||
sent ut: RomM 2026-08-23 12:05:27
|
||||
sent ut: Kimai 2026-08-23 12:05:27
|
||||
sent ut: Paperless-ngx 2026-08-23 12:05:27
|
||||
|
||||
THE THREE COUNTS:
|
||||
attempted (rows written): 3
|
||||
sent : 3
|
||||
suppressed : 0
|
||||
+1803
File diff suppressed because it is too large
Load Diff
@@ -0,0 +1,19 @@
|
||||
-- restoring the three burst subjects --
|
||||
2026-08-23T12:08:39Z
|
||||
bookstack Up 10 hours (healthy)
|
||||
bookstack-db Up 3 hours (healthy)
|
||||
calibre-web Up 4 minutes (healthy)
|
||||
docmost Up 6 hours (healthy)
|
||||
docmost-postgres Up 6 hours (healthy)
|
||||
docmost-redis Up 6 hours (healthy)
|
||||
filebrowser Up 44 hours (healthy)
|
||||
kimai Up 52 seconds (healthy)
|
||||
kimai-db Up About a minute (healthy)
|
||||
opengist Up 4 minutes (healthy)
|
||||
paperless-postgres Up 40 seconds (healthy)
|
||||
paperless-redis Up 40 seconds (healthy)
|
||||
paperless-webserver Up 30 seconds (health: starting)
|
||||
privatebin Up 2 hours (healthy)
|
||||
romm Up 41 seconds (healthy)
|
||||
romm-db Up 51 seconds (healthy)
|
||||
romm-redis Up 51 seconds (healthy)
|
||||
@@ -0,0 +1,9 @@
|
||||
### RED-PROOF 1 (R-389) — mutation: cooldownStackSuffix removed from the key ###
|
||||
### layer: processOperator's KEY — where the collapse happens ###
|
||||
--- FAIL: TestR389_TwoAppsInsideTheHourBothReachTheOperator (0.02s)
|
||||
r389_cooldown_grain_test.go:180: 2 apps down inside the hour produced 1 operator mail(s), want 2 (suppressed=1). This is R-389: the second app's alarm took the first app's cooldown slot.
|
||||
--- FAIL: TestR389_SameAppTwiceInsideTheHourIsStillSuppressed (0.02s)
|
||||
r389_cooldown_grain_test.go:220: the suppression row does not name the app in its key — that visibility is R-182's contribution and is how this defect was found: [sent | Telepített alkalmazás nem fut: BookStack | suppressed | Telepített alkalmazás nem fut: BookStack | operator cooldown 1h, key=c1:app_start_failed]
|
||||
FAIL
|
||||
FAIL gitea.dooplex.hu/admin/felhom-hub/internal/notify 0.166s
|
||||
FAIL
|
||||
+12
@@ -0,0 +1,12 @@
|
||||
### RED-PROOF 2 (R-389) — mutation: allow-list removed, suffix applied globally ###
|
||||
### layer: cooldownStackSuffix's REGISTER — the fence that keeps the backup family coarse ###
|
||||
--- FAIL: TestR389_StackSuffixIsAllowListedAndFailSoft (0.00s)
|
||||
--- FAIL: TestR389_StackSuffixIsAllowListedAndFailSoft/crossdrive_failed_is_NOT_split_per_app (0.00s)
|
||||
r389_cooldown_grain_test.go:58: cooldownStackSuffix("crossdrive_failed", "{\"stack_name\":\"bookstack\",\"method\":\"rsync\"}") = ":bookstack", want ""
|
||||
--- FAIL: TestR389_StackSuffixIsAllowListedAndFailSoft/app_deployed_is_not_in_the_register (0.00s)
|
||||
r389_cooldown_grain_test.go:58: cooldownStackSuffix("app_deployed", "{\"stack_name\":\"bookstack\",\"display_name\":\"BookStack\"}") = ":bookstack", want ""
|
||||
--- FAIL: TestR389_StackSuffixIsAllowListedAndFailSoft/app_removed_is_not_in_the_register (0.00s)
|
||||
r389_cooldown_grain_test.go:58: cooldownStackSuffix("app_removed", "{\"stack_name\":\"bookstack\",\"display_name\":\"BookStack\"}") = ":bookstack", want ""
|
||||
--- FAIL: TestR389_StackSuffixIsAllowListedAndFailSoft/backup_failed_is_not_in_the_register (0.00s)
|
||||
r389_cooldown_grain_test.go:58: cooldownStackSuffix("backup_failed", "{\"stack_name\":\"bookstack\",\"display_name\":\"BookStack\"}") = ":bookstack", want ""
|
||||
--- FAIL: TestR389_NoOtherEventTypeKeyChanges (0.00s)
|
||||
Reference in New Issue
Block a user