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 wrong: in the event log, a delivery to a deleted target, shown as for example "Debug log (deleted)", still has a Replay button. Pressing it answers "Not replayed: the target this delivery was for has been deleted. Recreate the target, then replay." That advice cannot work. Recreating the target makes a new one, and the old delivery still names the deleted target, so the replay is refused again. The action that sends the event to the new target is Resubmit. (templates/source_logs.html; replayOutcome in internal/handlers/delivery_replay.go)
Definition of done:
A delivery whose target is deleted has no Replay button. Its row says that the target was deleted.
The refusal message, which an old page left open can still reach, tells the operator to use Resubmit to send the event to the webhook's current targets.
Tests: no Replay button on a delivery to a deleted target, and the new message text.
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 wrong: in the event log, a delivery to a deleted target, shown as for example "Debug log (deleted)", still has a Replay button. Pressing it answers "Not replayed: the target this delivery was for has been deleted. Recreate the target, then replay." That advice cannot work. Recreating the target makes a new one, and the old delivery still names the deleted target, so the replay is refused again. The action that sends the event to the new target is Resubmit. (`templates/source_logs.html`; `replayOutcome` in `internal/handlers/delivery_replay.go`)
Definition of done:
- A delivery whose target is deleted has no Replay button. Its row says that the target was deleted.
- The refusal message, which an old page left open can still reach, tells the operator to use Resubmit to send the event to the webhook's current targets.
- Tests: no Replay button on a delivery to a deleted target, and the new message text.
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 wrong: in the event log, a delivery to a deleted target, shown as for example "Debug log (deleted)", still has a Replay button. Pressing it answers "Not replayed: the target this delivery was for has been deleted. Recreate the target, then replay." That advice cannot work. Recreating the target makes a new one, and the old delivery still names the deleted target, so the replay is refused again. The action that sends the event to the new target is Resubmit. (
templates/source_logs.html;replayOutcomeininternal/handlers/delivery_replay.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