R-1251 (P1): a pending put-back blocks every start — a cut restore's copy on an unbound drive waits (a restore hold), is poured back when the drive binds before any start; a failed put-back holds the app (H2); Stop during a restore still puts back (H7). Commit only, unreleased.
gates / gates (push) Successful in 1m18s
gates / gates (push) Successful in 1m18s
This commit is contained in:
1 parent
2449223f10
commit
bb2809dc68
16 files changed
+847
-24
No files matched your search
@@ -1653,6 +1653,7 @@
|
||||
"hold.copy_holds.files": "holds the settings, the database and the files",
|
||||
"hold.copy_holds.volumes": "holds the settings, the database and the data volumes",
|
||||
"hold.unhealthy_stop.repeat": "We stopped the app again because it kept crashing (or ran out of memory). Felhom support has been told. Press Start to try again.",
|
||||
"hold.putback_pending": "Restoring %s was interrupted. Its data from before the restore is on a drive that is not available now. When the drive is back, the box puts that data back and starts the app. Until then the app does not start.",
|
||||
"hold.unhealthy_stop": "We stopped the app because it kept crashing (or ran out of memory). Press Start to try again.",
|
||||
"hold.update.no_whole_copy": "The update of %s did not work, and neither did the automatic undo. This box has no copy that can bring the app back together with its files. Felhom support has been told — until then, do not restart the app or delete its data.",
|
||||
"hold.update.sentence": "The update of %s at %s did not succeed, and the app did not start on the new version. The app stays stopped for safety, so that its data is not damaged. It can be restored on the Backups page from this backup: %s, %s — this copy %s.",
|
||||
|
||||
Reference in new issue
Block a user