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 entrypoint list on the webhook page (templates/source_detail.html) shows each entrypoint's description, URL and active state, but not whether anything is using it. It shows no count of events received and no time of the last one, even though each event records its entrypoint (Event.EntrypointID). With several entrypoints, an operator cannot tell which senders are live before deactivating or deleting one.
Definition of done:
Each entrypoint shows when its last event arrived (relative, with the full UTC time on hover), or "never".
Each entrypoint shows how many events arrived through it within the webhook's retention period.
No full scan per page view: one query, grouped by entrypoint, over an index on the entrypoint and the time received. Pre-1.0, so any new index is added to the schema in place.
Tests: two entrypoints with different traffic show their own figures, and an unused one shows "never".
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 entrypoint list on the webhook page (`templates/source_detail.html`) shows each entrypoint's description, URL and active state, but not whether anything is using it. It shows no count of events received and no time of the last one, even though each event records its entrypoint (`Event.EntrypointID`). With several entrypoints, an operator cannot tell which senders are live before deactivating or deleting one.
Definition of done:
- Each entrypoint shows when its last event arrived (relative, with the full UTC time on hover), or "never".
- Each entrypoint shows how many events arrived through it within the webhook's retention period.
- No full scan per page view: one query, grouped by entrypoint, over an index on the entrypoint and the time received. Pre-1.0, so any new index is added to the schema in place.
- Tests: two entrypoints with different traffic show their own figures, and an unused one shows "never".
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 entrypoint list on the webhook page (
templates/source_detail.html) shows each entrypoint's description, URL and active state, but not whether anything is using it. It shows no count of events received and no time of the last one, even though each event records its entrypoint (Event.EntrypointID). With several entrypoints, an operator cannot tell which senders are live before deactivating or deleting one.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