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, in the event log (templates/source_logs.html; deliveryResultColumns in internal/handlers/delivery_result_view.go):
Each attempt shows its number, outcome, status code and duration, but not when it was made. Its stored time is not even loaded. A delivery that retried over an hour looks the same as one that retried within a second.
A delivery does not show when it was created. A replay adds a second row with the same target name and status as the original, and nothing says which row is the replay. In the audit, after one replay the event's summary line read "Fulfilment: delivered" twice.
Event times are printed as "2026-10-01 19:56:55" with no time zone. The webhook page prints the same kind of time with "UTC".
Definition of done:
Each attempt shows when it ran, and each delivery shows when it was created.
A delivery created by Replay is labelled as a replay, both in the event's summary line and in its delivery list.
Every time in the event log carries its zone, in the same style as the recent events list after #347: relative, with the full UTC time on hover.
Pre-1.0: if marking replays needs a new column, it goes into the schema in place, with no migration.
Tests: the attempt time, the delivery time, the replay label, and the zone on event times.
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, in the event log (`templates/source_logs.html`; `deliveryResultColumns` in `internal/handlers/delivery_result_view.go`):
- Each attempt shows its number, outcome, status code and duration, but not when it was made. Its stored time is not even loaded. A delivery that retried over an hour looks the same as one that retried within a second.
- A delivery does not show when it was created. A replay adds a second row with the same target name and status as the original, and nothing says which row is the replay. In the audit, after one replay the event's summary line read "Fulfilment: delivered" twice.
- Event times are printed as "2026-10-01 19:56:55" with no time zone. The webhook page prints the same kind of time with "UTC".
Definition of done:
- Each attempt shows when it ran, and each delivery shows when it was created.
- A delivery created by Replay is labelled as a replay, both in the event's summary line and in its delivery list.
- Every time in the event log carries its zone, in the same style as the recent events list after https://git.eeqj.de/sneak/webhooker/issues/347: relative, with the full UTC time on hover.
- Pre-1.0: if marking replays needs a new column, it goes into the schema in place, with no migration.
- Tests: the attempt time, the delivery time, the replay label, and the zone on event times.
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:19 +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, in the event log (
templates/source_logs.html;deliveryResultColumnsininternal/handlers/delivery_result_view.go):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