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 event log lists every event, 25 to a page (HandleSourceLogs in internal/handlers/source_management.go). There is no way to list only the events that have a failed delivery. Today that means paging and expanding by hand. Once #349 cuts the log to the 50 most recent events, a failure older than those cannot be found from the UI at all.
Definition of done:
The event log has a control to show only events with at least one failed delivery, and one to show only events with a delivery still pending or retrying. Each control shows how many events match.
The filtered list applies the same row limit as the unfiltered one.
The filter queries delivery status through the existing status index (idx_deliveries_status). It never reads event bodies to decide.
Tests: each filter returns exactly the matching events, and its count matches the list.
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 event log lists every event, 25 to a page (`HandleSourceLogs` in `internal/handlers/source_management.go`). There is no way to list only the events that have a failed delivery. Today that means paging and expanding by hand. Once https://git.eeqj.de/sneak/webhooker/issues/349 cuts the log to the 50 most recent events, a failure older than those cannot be found from the UI at all.
Definition of done:
- The event log has a control to show only events with at least one failed delivery, and one to show only events with a delivery still pending or retrying. Each control shows how many events match.
- The filtered list applies the same row limit as the unfiltered one.
- The filter queries delivery status through the existing status index (`idx_deliveries_status`). It never reads event bodies to decide.
- Tests: each filter returns exactly the matching events, and its count matches the list.
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:20 +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 event log lists every event, 25 to a page (
HandleSourceLogsininternal/handlers/source_management.go). There is no way to list only the events that have a failed delivery. Today that means paging and expanding by hand. Once #349 cuts the log to the 50 most recent events, a failure older than those cannot be found from the UI at all.Definition of done:
idx_deliveries_status). It never reads event bodies to decide.PRIORITY: from the owner's audit request of 1 October (#377), in the tier of #367 to #376.
Model: opus-5-5