3 Commits

Include renames

Author	SHA1	Message	Date
clawbot	ded39aa158	Use one recovery routine at start and on every sweep tick (closes #542) ... Start-up recovery and the 60-second sweep were two parallel sets of functions doing the same job. recoverDeliveries now does it, run once at start and then on every tick from one goroutine. A retrying delivery is scheduled after what is left of its backoff, now if nothing is left, so backoffElapsed is gone. The run at start still takes every pending delivery and opens a webhook database whose file is missing; a tick still takes only pending deliveries untouched for 15 minutes, at most 500, and skips a missing file. A retrying delivery is taken before its event is read. The README describes one routine. Model: opus-5-5	2026-10-15 21:57:05 +02:00
clawbot	89b2dadd48	Read queue depths with Find, not Scan (closes #234) (#237) ... Both queue-depth reads used (*gorm.DB).Scan, which swaps GORM's own trace recorder in for the logging adapter. That recorder does not implement gorm.ParamsFilter, so those statements logged their bound values interpolated, bypassing the suppression added for #207. The scan guard from #222 and the queue-depth sampler from #224 each gated green against a next that lacked the other; both landed and next went red. Converted to Find. The emitted SQL is identical apart from placeholders, and both paths parse the anonymous dest schema the same way, so the queue-depth gauges are unchanged.	2026-08-20 07:55:20 +02:00
clawbot	4cc83b2326	Expose delivery metrics on /metrics (closes #209) (#224)	2026-08-20 07:19:04 +02:00