log: write durations as text, not nanoseconds (closes #228) #239

Merged
clawbot merged 1 commits from issue-228-log-durations-readable into next 2026-10-02 08:37:48 +02:00
1 Commits
Author SHA1 Message Date
sneak 68c3c66061 log: write durations as text, not nanoseconds (closes #228)
check / check (push) Successful in 1m21s
The JSON log wrote a Go duration as a bare count of nanoseconds, so
the watcher starting line showed dnsInterval 120000000000 for 2m and a
delivery retry showed retryIn 1015437050. Each duration logged is now
passed through its String() form: dnsInterval and tlsInterval when the
watcher starts, retryIn on a delivery retry, and latency on a
succeeded port check. A test checks that retryIn is logged as the
text of the wait the retry actually took.

The request log's latency_ms is left as it is: its key names its
unit.

Model: opus-5-5
2026-10-02 06:35:40 +00:00