quak (https://git.eeqj.de/sneak/quak) backs up an Ente photo account with quak backup. Its README sets the backup up in cron, with every night's output appended to one file, ~/quak-backup.log. No line of that output carries a date or a time. A reader of the log cannot tell which night printed which lines, or when the last failed run was.
A night's output today:
Starting backup...
Refreshing library...
Fetching ML data...
--- Backup complete ---
Total files: 4
Downloaded: 0
Skipped: 4
Failed: 0
Question: should quak backup print the date and time of each run?
Dated runs: the first line and the --- Backup complete --- line carry the local date and time, for example Starting backup at 2026-11-11 03:30:00 +0100. Every other line stays as it is.
As now: users who want dates add them in their crontab, for example by running date into the same log first.
Recommendation: Dated runs. It changes two lines, and the README's own crontab then produces a log that can be read.
Model: opus-5-5
quak (https://git.eeqj.de/sneak/quak) backs up an Ente photo account with `quak backup`. Its README sets the backup up in cron, with every night's output appended to one file, `~/quak-backup.log`. No line of that output carries a date or a time. A reader of the log cannot tell which night printed which lines, or when the last failed run was.
A night's output today:
```
Starting backup...
Refreshing library...
Fetching ML data...
--- Backup complete ---
Total files: 4
Downloaded: 0
Skipped: 4
Failed: 0
```
**Question: should `quak backup` print the date and time of each run?**
- Dated runs: the first line and the `--- Backup complete ---` line carry the local date and time, for example `Starting backup at 2026-11-11 03:30:00 +0100`. Every other line stays as it is.
- As now: users who want dates add them in their crontab, for example by running `date` into the same log first.
Recommendation: Dated runs. It changes two lines, and the README's own crontab then produces a log that can be read.
Model: opus-5-5
sneak
was assigned by clawbot2026-11-11 21:22:24 +01:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
quak (https://git.eeqj.de/sneak/quak) backs up an Ente photo account with
quak backup. Its README sets the backup up in cron, with every night's output appended to one file,~/quak-backup.log. No line of that output carries a date or a time. A reader of the log cannot tell which night printed which lines, or when the last failed run was.A night's output today:
Question: should
quak backupprint the date and time of each run?--- Backup complete ---line carry the local date and time, for exampleStarting backup at 2026-11-11 03:30:00 +0100. Every other line stays as it is.dateinto the same log first.Recommendation: Dated runs. It changes two lines, and the README's own crontab then produces a log that can be read.
Model: opus-5-5