Files
felhom.eu/documentation/audits/the-28-2026-09-22/apps/calcom/verdict.json
T
admin 1de6aaf904
gates / gates (push) Successful in 25s
corrections: calibre-web restore was REFUSED, calcom was INCONCLUSIVE
Both from their own records, not re-run.

calibre-web: the flash_error refusal is in its log; that walk predated the refusal-capture code.
The report's own prose already said so while the table disagreed.

calcom: the restore was accepted and the app read running; the classifier then saw "starting", a
settling state it did not list beside running/unhealthy, and fell through to failed. The brief
supposed a read-back artefact - that is wrong, and restore_state_seen says so.

Restores correctly refused: 2 -> 3.

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

46 lines
2.2 KiB
JSON

{
"harness_version": 2,
"app": "calcom",
"venue": "guest 9202 demo-hp-scratch, controller 0.261.0, drill catalog",
"class": "db",
"from": {
"calcom": "calcom/cal.com:v6.2.0",
"calcom-postgres": "postgres:16-alpine"
},
"to": {},
"verdict": "no-edge",
"deployed": true,
"seed_route": "none written",
"seed_read_before": false,
"seed_read_after_update": false,
"backup": {
"snapshots_offered": 1,
"first": {
"time": "2026-09-22T13:32:12Z",
"short_id": "helyi",
"tier": 1,
"drive_label": "Belső SSD (rendszer)"
}
},
"restore_verdict": "inconclusive",
"seed_read_after_restore": false,
"healthy_after": false,
"migration_observed": null,
"removed_clean": true,
"edge": null,
"duration_s": 675.8,
"measured_at": "2026-09-22T13:26:57.631421+00:00",
"evidence": "the-28-2026-09-22/apps/calcom/",
"notes": [
"no fixture: no non-browser seed route was written for this app"
],
"front_door_after_deploy": {
"rc": 0,
"code": "502"
},
"restore_raw": "{'ok': True, 'snapshot_id': 'helyi', 'snapshots': [{'time': '2026-09-22T13:32:12Z', 'short_id': 'helyi', 'tier': 1, 'drive_label': 'Belső SSD (rendszer)'}], 'http': 'HTTP/2 302', 'location': ['location: /backups/restore?flash=flash.restore.started'], 'seconds': 44.6, 'state_after': 'running', 'hold_after': None, 'observables_after': {'pinned_images': {'calcom': 'calcom/cal.com:v6.2.0', 'calcom-pos",
"restore_refusal": null,
"restore_state_seen": "starting",
"remove_leftovers": "",
"correction": "Recorded `failed`, and that was the HARNESS, not the product. The restore was accepted (`flash=flash.restore.started`, no `flash_error`), the app read `running` at +45 s with no hold and no phase, and the classifier then looked once more and saw **`starting`** — a settling state it did not list alongside `running`/`unhealthy`, so it fell through to `failed`. NOT, as the task brief supposed, a read-back of data that was never seeded: the seed half is recorded separately and was already `no route`. `inconclusive` is the honest verdict — the restore ran and nothing says it did not work, and nothing proves it did. Corrected 2026-09-22 from log.txt 15:32:13-15:33:17 and the record's own `restore_state_seen`, not re-run."
}