webhooker

239 Commits 5 Branches 0 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
sneak	d66292df43	Show a target paused by its circuit breaker (closes #385 ) check / check (push) Successful in 3m21s Details While an http or slack target's circuit breaker is open, the target's row on the webhook page says its deliveries are paused until the cooldown ends, in UTC and from now. Each of its retrying deliveries shows as waiting in the event log and on the event's page, until the later of the cooldown's end and the end of its own backoff. While the breaker is half-open, the row says deliveries are held while one delivery tests the target, with no time, and deliveries keep their plain status. The engine gains one read, StateAndCooldown(targetID), taking a breaker's state and remaining cooldown under one lock; the handlers reach it through a one-method interface wired like Archives. Model: opus-5-5	2026-10-02 23:16:44 +00:00
clawbot	9305af4f85	Show each target's delivered and failed deliveries in the target list (closes #372 ) check / check (push) Successful in 3m17s Details The target list showed nothing about how a target's deliveries were going. Each target now shows Delivered and Failed, each in total and in the last 24 hours. The totals are the per-target running totals kept for the statistics pane, so retention does not reduce them; the 24-hour figures are one count over the deliveries' final-status index, for all of the webhook's targets at once. Pending and retrying deliveries count in neither. If the event database cannot be read, each row says so instead of showing zeros. The archive details and Download button on database targets are kept. Model: opus-5-5	2026-10-02 23:47:16 +02:00
clawbot	2967c475a1	Show a database target's archive file, size and last write in the target list (closes #397 ) check / check (push) Successful in 3m17s Details For a database target, the target list showed only its expiry, so the archive file the README's backup and move-away advice depend on could only be found from a shell on the host. Each database target now shows its archive file's name, its size on disk (the file and its -wal together) and when it was last written, relative with the full UTC time on hover, all from the files' metadata without opening the archive. Before the first write, and after the file has been moved away, it shows the name and "not created yet". Tests cover all three states. Model: opus-5-5	2026-10-02 21:22:33 +02:00

Author

SHA1

Message

Date

sneak

d66292df43

Show a target paused by its circuit breaker (closes #385 )

check / check (push) Successful in 3m21s

Details

While an http or slack target's circuit breaker is open, the target's
row on the webhook page says its deliveries are paused until the
cooldown ends, in UTC and from now. Each of its retrying deliveries
shows as waiting in the event log and on the event's page, until the
later of the cooldown's end and the end of its own backoff. While the
breaker is half-open, the row says deliveries are held while one
delivery tests the target, with no time, and deliveries keep their
plain status.

The engine gains one read, StateAndCooldown(targetID), taking a
breaker's state and remaining cooldown under one lock; the handlers
reach it through a one-method interface wired like Archives.

Model: opus-5-5

2026-10-02 23:16:44 +00:00

clawbot

9305af4f85

Show each target's delivered and failed deliveries in the target list (closes #372 )

check / check (push) Successful in 3m17s

Details

The target list showed nothing about how a target's deliveries were going. Each target now shows Delivered and Failed, each in total and in the last 24 hours. The totals are the per-target running totals kept for the statistics pane, so retention does not reduce them; the 24-hour figures are one count over the deliveries' final-status index, for all of the webhook's targets at once. Pending and retrying deliveries count in neither. If the event database cannot be read, each row says so instead of showing zeros. The archive details and Download button on database targets are kept.

Model: opus-5-5

2026-10-02 23:47:16 +02:00

clawbot

2967c475a1

Show a database target's archive file, size and last write in the target list (closes #397 )

check / check (push) Successful in 3m17s

Details

For a database target, the target list showed only its expiry, so the archive file the README's backup and move-away advice depend on could only be found from a shell on the host. Each database target now shows its archive file's name, its size on disk (the file and its -wal together) and when it was last written, relative with the full UTC time on hover, all from the files' metadata without opening the archive. Before the first write, and after the file has been moved away, it shows the name and "not created yet". Tests cover all three states.

Model: opus-5-5

2026-10-02 21:22:33 +02:00