admin
5a349d9884
gates / gates (push) Successful in 26s
- 09 §3: decision 19 (the copy method is chosen by a bake-off) and 20 (the full-system backup waits for the update leg, inside its window; built later). - Bake-off on 9202, docmost / romm / vikunja: both methods pass every case; the folder copy wins because an app with no database server gets no dump, so dump-and-load would need the folder copy anyway. 1-5 s extra downtime, ~420 MB/s, disk = the volumes. - R-645 filed: lifting an update hold by hand lets the recovery unit be re-captured with the failed definition within seconds. Documents and evidence only; product code follows in the controller. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
14 lines
608 B
Plaintext
14 lines
608 B
Plaintext
10:19:56 === undo by F: vikunja
|
|
10:20:14 [INFO] [settings] restore hold CLEARED for vikunja
|
|
|
|
10:20:16 pinned_images:
|
|
vikunja: vikunja/vikunja:2.3.0
|
|
|
|
10:20:16 hold lift + pin back took 20.2 s (not part of a product undo)
|
|
10:20:19 volumes put back in 0.90s
|
|
|
|
10:20:19 product start -> 200
|
|
10:20:22 vikunja: readback of the seeded project http=200 ok=True
|
|
10:20:22 vikunja B: project readback=True attachment content readback=True
|
|
10:20:24 F RESULT: healthy=True after 2.7s A=True B=True db now: tables=36 ledger=117 newest=SCHEMA_INIT (before the update: tables=36 ledger=117 newest=SCHEMA_INIT)
|