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
9 lines
414 B
Plaintext
9 lines
414 B
Plaintext
10:21:58 === undo by D: vikunja
|
|
10:22:16 [INFO] [settings] restore hold CLEARED for vikunja
|
|
|
|
10:22:18 pinned_images:
|
|
vikunja: vikunja/vikunja:2.3.0
|
|
|
|
10:22:18 hold lift + pin back took 20.1 s (not part of a product undo)
|
|
10:22:18 vikunja has no database server: the product wrote NO safety dump (R-641). D's copy for it is a volume tar at safety-dump time, which is F with extra steps — recorded, not re-run.
|