quak backup now prints two new lines, as sneak asked on the issue ("add lines, don't change existing"):
Started at 2026-11-11 03:30:00 +0100 right after Starting backup..., printed on every run, including one refused by the lock.
Finished at … right after --- Backup complete ---. Like the rest of that summary, it is left out with --json.
The time is local, with its offset from UTC. Commands get the time from a new now field on CliContext. bin/quak.ts passes () => new Date(), and tests pass fixed times.
The README crontab now pipes output to logger -t quak, which writes to the journal under systemd and adds its own timestamp. Appending to a file is still described as the alternative, where the new lines date each run.
Tests that compare exact stderr set the time zone to Europe/Berlin. backup-end-to-end.test.ts sets it at module scope, before its fixtures compute local noon, so the folder date and the printed time use the same zone. A new test checks the offset format in three zones: +0100, +0530 and -0500.
Model: opus-5-5
closes https://git.eeqj.de/sneak/quak/issues/245
`quak backup` now prints two new lines, as sneak asked on the issue ("add lines, don't change existing"):
- `Started at 2026-11-11 03:30:00 +0100` right after `Starting backup...`, printed on every run, including one refused by the lock.
- `Finished at …` right after `--- Backup complete ---`. Like the rest of that summary, it is left out with `--json`.
The time is local, with its offset from UTC. Commands get the time from a new `now` field on `CliContext`. `bin/quak.ts` passes `() => new Date()`, and tests pass fixed times.
The README crontab now pipes output to `logger -t quak`, which writes to the journal under systemd and adds its own timestamp. Appending to a file is still described as the alternative, where the new lines date each run.
Tests that compare exact stderr set the time zone to `Europe/Berlin`. `backup-end-to-end.test.ts` sets it at module scope, before its fixtures compute local noon, so the folder date and the printed time use the same zone. A new test checks the offset format in three zones: `+0100`, `+0530` and `-0500`.
Model: opus-5-5
Adds a `Started at` line after `Starting backup...` and a `Finished at`
line after `--- Backup complete ---`, in local time with the UTC offset.
No existing line changes. The clock comes in through `CliContext.now`.
The README's crontab now pipes the output to `logger`, which adds its own
time to each line; appending to a file remains as the alternative.
Model: opus-5-5
The change does what #245 asks: dated Started at and Finished at lines, no existing line changed, and the README crontab piping to logger.
Deviation: one README sentence called Started at the run's first line; I pushed a correction on top of this head, and that commit needs its own review.
Model: opus-5-5
Verdict: PASS
Head: ab236dc162772f328fa52f63e5692914b1f9961d
The change does what https://git.eeqj.de/sneak/quak/issues/245 asks: dated `Started at` and `Finished at` lines, no existing line changed, and the README crontab piping to `logger`.
- Deviation: one README sentence called `Started at` the run's first line; I pushed a correction on top of this head, and that commit needs its own review.
Model: opus-5-5
The change meets #245: quak backup adds dated Started at and Finished at lines without changing any existing line, and the README crontab now pipes its output to logger.
Model: opus-5-5
Verdict: PASS
Head: 94bef69403f7b1ed72305307ccf866bda7ed2ae3
The change meets https://git.eeqj.de/sneak/quak/issues/245: `quak backup` adds dated `Started at` and `Finished at` lines without changing any existing line, and the README crontab now pipes its output to `logger`.
Model: opus-5-5
clawbot
merged commit ecdd90b0a8 into next2026-11-19 08:47:07 +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.
closes #245
quak backupnow prints two new lines, as sneak asked on the issue ("add lines, don't change existing"):Started at 2026-11-11 03:30:00 +0100right afterStarting backup..., printed on every run, including one refused by the lock.Finished at …right after--- Backup complete ---. Like the rest of that summary, it is left out with--json.The time is local, with its offset from UTC. Commands get the time from a new
nowfield onCliContext.bin/quak.tspasses() => new Date(), and tests pass fixed times.The README crontab now pipes output to
logger -t quak, which writes to the journal under systemd and adds its own timestamp. Appending to a file is still described as the alternative, where the new lines date each run.Tests that compare exact stderr set the time zone to
Europe/Berlin.backup-end-to-end.test.tssets it at module scope, before its fixtures compute local noon, so the folder date and the printed time use the same zone. A new test checks the offset format in three zones:+0100,+0530and-0500.Model: opus-5-5
Starting backup...Verdict: PASS
Head:
ab236dc162The change does what #245 asks: dated
Started atandFinished atlines, no existing line changed, and the README crontab piping tologger.Started atthe run's first line; I pushed a correction on top of this head, and that commit needs its own review.Model: opus-5-5
Verdict: PASS
Head:
94bef69403The change meets #245:
quak backupadds datedStarted atandFinished atlines without changing any existing line, and the README crontab now pipes its output tologger.Model: opus-5-5