audit the whole app for stupid cases of missing functionality or basic things like this (like the stats panel at the top that i requested).
What is missing: the webhook list (templates/sources_list.html, buildWebhookListItems in internal/handlers/source_management.go) shows each webhook's name, description, retention, and counts of entrypoints, targets and events. It does not show when a webhook last received an event, or whether its deliveries are failing. A broken webhook looks exactly like a healthy one until its page is opened. The entrypoint and target counts also include inactive ones without saying so.
Definition of done:
Each webhook in the list shows when its last event arrived, or "no events yet".
Each webhook shows how many deliveries failed in the last 24 hours, highlighted when that is not zero.
Those figures reuse the counts from #368 rather than computing them again.
The entrypoint and target counts say how many are inactive, for example "4 targets, 1 inactive".
Tests: a webhook with recent failures, a healthy one, and one with no events each show the right figures.
PRIORITY: from the owner's audit request of 1 October (#377), in the tier of #367 to #376.
Model: opus-5-5
Owner's request, https://git.eeqj.de/sneak/webhooker/issues/377 (chat, 2026-10-01):
> audit the whole app for stupid cases of missing functionality or basic things like this (like the stats panel at the top that i requested).
What is missing: the webhook list (`templates/sources_list.html`, `buildWebhookListItems` in `internal/handlers/source_management.go`) shows each webhook's name, description, retention, and counts of entrypoints, targets and events. It does not show when a webhook last received an event, or whether its deliveries are failing. A broken webhook looks exactly like a healthy one until its page is opened. The entrypoint and target counts also include inactive ones without saying so.
Definition of done:
- Each webhook in the list shows when its last event arrived, or "no events yet".
- Each webhook shows how many deliveries failed in the last 24 hours, highlighted when that is not zero.
- Those figures reuse the counts from https://git.eeqj.de/sneak/webhooker/issues/368 rather than computing them again.
- The entrypoint and target counts say how many are inactive, for example "4 targets, 1 inactive".
- Tests: a webhook with recent failures, a healthy one, and one with no events each show the right figures.
PRIORITY: from the owner's audit request of 1 October (https://git.eeqj.de/sneak/webhooker/issues/377), in the tier of https://git.eeqj.de/sneak/webhooker/issues/367 to https://git.eeqj.de/sneak/webhooker/issues/376.
Model: opus-5-5
clawbot
self-assigned this 2026-10-01 22:06:25 +02: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.
Owner's request, #377 (chat, 2026-10-01):
What is missing: the webhook list (
templates/sources_list.html,buildWebhookListItemsininternal/handlers/source_management.go) shows each webhook's name, description, retention, and counts of entrypoints, targets and events. It does not show when a webhook last received an event, or whether its deliveries are failing. A broken webhook looks exactly like a healthy one until its page is opened. The entrypoint and target counts also include inactive ones without saying so.Definition of done:
PRIORITY: from the owner's audit request of 1 October (#377), in the tier of #367 to #376.
Model: opus-5-5