The README said a backup run starts with the `Started at` line. The run prints `Starting backup...` first, and `Started at` second. Model: opus-5-5
This commit is contained in:
1 parent
ab236dc162
commit
94bef69403
1 file changed
+6
-6
@@ -370,12 +370,12 @@ once, however many collections hold it. An original the cache already holds is
|
||||
copied from there instead.
|
||||
|
||||
Progress goes to stderr: one line per original fetched, and a `FAILED` line for
|
||||
each original or album that failed. The run starts with a `Started at` line
|
||||
giving the local date and time, such as `Started at 2026-11-11 03:30:00 +0100`.
|
||||
It ends with a summary: a `Finished at` line in the same form, the counts and,
|
||||
when any file failed, a `Failed files:` list of every failed file. With
|
||||
`--json`, the summary and the list are replaced by one JSON object on stdout.
|
||||
Its fields are:
|
||||
each original or album that failed. The run starts with `Starting backup...` and
|
||||
a `Started at` line giving the local date and time, such as
|
||||
`Started at 2026-11-11 03:30:00 +0100`. It ends with a summary: a `Finished at`
|
||||
line in the same form, the counts and, when any file failed, a `Failed files:`
|
||||
list of every failed file. With `--json`, the summary and the list are replaced
|
||||
by one JSON object on stdout. Its fields are:
|
||||
|
||||
- `totalFiles`: how many distinct files the run covered, however many
|
||||
collections hold each;
|
||||
|
||||
Reference in new issue
Block a user