README promises replay (README.md:174) and full request/response logging, but no replay exists and templates/source_logs.html:26-30 renders only the delivery status string — no status code, error, response body, or duration per attempt.
Done: per-attempt results (status code, error, response body, duration) visible in the UI, and a redeliver action for an event — or the README claims removed if deferred, with this issue split accordingly.
From audit #303 (significant).
README promises replay (`README.md:174`) and full request/response logging, but no replay exists and `templates/source_logs.html:26-30` renders only the delivery status string — no status code, error, response body, or duration per attempt.
Done: per-attempt results (status code, error, response body, duration) visible in the UI, and a redeliver action for an event — or the README claims removed if deferred, with this issue split accordingly.
Already addressed before this audit ran: per-delivery replay (#203), per-attempt results with status code, error, response body and duration in the event log (#202), and event resubmit (#250) all ship on next; see templates/source_logs.html and internal/handlers/delivery_replay.go. Closing.
Model: fable-5-1
Already addressed before this audit ran: per-delivery replay (https://git.eeqj.de/sneak/webhooker/issues/203), per-attempt results with status code, error, response body and duration in the event log (https://git.eeqj.de/sneak/webhooker/issues/202), and event resubmit (https://git.eeqj.de/sneak/webhooker/issues/250) all ship on `next`; see `templates/source_logs.html` and `internal/handlers/delivery_replay.go`. Closing.
Model: fable-5-1
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.
From audit #303 (significant).
README promises replay (
README.md:174) and full request/response logging, but no replay exists andtemplates/source_logs.html:26-30renders only the delivery status string — no status code, error, response body, or duration per attempt.Done: per-attempt results (status code, error, response body, duration) visible in the UI, and a redeliver action for an event — or the README claims removed if deferred, with this issue split accordingly.
Already addressed before this audit ran: per-delivery replay (#203), per-attempt results with status code, error, response body and duration in the event log (#202), and event resubmit (#250) all ship on
next; seetemplates/source_logs.htmlandinternal/handlers/delivery_replay.go. Closing.Model: fable-5-1