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, every attempt of a database or log target reads "success Status: — (no response)". Those targets make no HTTP request, so there is no response to have. "No response" reads like a failed connection, and for an http target that is exactly what the same words mean. (templates/source_logs.html)
Definition of done:
An attempt by a database or log target says what happened in that target's own terms, for example "archived" or "written to the log", and shows no status field.
http and slack attempts are unchanged.
Tests: one per target type.
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, every attempt of a `database` or `log` target reads "success Status: — (no response)". Those targets make no HTTP request, so there is no response to have. "No response" reads like a failed connection, and for an `http` target that is exactly what the same words mean. (`templates/source_logs.html`)
Definition of done:
- An attempt by a `database` or `log` target says what happened in that target's own terms, for example "archived" or "written to the log", and shows no status field.
- `http` and `slack` attempts are unchanged.
- Tests: one per target type.
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
An attempt by a database or log target says what happened in that target's own terms ("archived", "written to the log") and shows no status field, in the event log and on the event's page, through the one shared delivery renderer from #465.
http and slack attempts are unchanged.
Tests: one per target type.
Model: opus-5-5
Plan.
- An attempt by a `database` or `log` target says what happened in that target's own terms ("archived", "written to the log") and shows no status field, in the event log and on the event's page, through the one shared delivery renderer from https://git.eeqj.de/sneak/webhooker/pulls/465.
- `http` and `slack` attempts are unchanged.
- Tests: one per target type.
Model: opus-5-5
#484: in the event log and on an event's page, a successful database attempt now reads "archived" and a successful log attempt "written to the log", with no status shown; http and slack attempts are unchanged. The change is in the one shared attempt template, with one test per target type.
Judgement call: a failed database or log attempt keeps the word "failure", since its error line already says what went wrong.
Model: opus-5-5
https://git.eeqj.de/sneak/webhooker/pulls/484: in the event log and on an event's page, a successful `database` attempt now reads "archived" and a successful `log` attempt "written to the log", with no status shown; `http` and `slack` attempts are unchanged. The change is in the one shared attempt template, with one test per target type.
Judgement call: a failed `database` or `log` attempt keeps the word "failure", since its error line already says what went wrong.
Model: opus-5-5
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, every attempt of a
databaseorlogtarget reads "success Status: — (no response)". Those targets make no HTTP request, so there is no response to have. "No response" reads like a failed connection, and for anhttptarget that is exactly what the same words mean. (templates/source_logs.html)Definition of done:
databaseorlogtarget says what happened in that target's own terms, for example "archived" or "written to the log", and shows no status field.httpandslackattempts are unchanged.PRIORITY: from the owner's audit request of 1 October (#377), in the tier of #367 to #376.
Model: opus-5-5
Plan.
databaseorlogtarget says what happened in that target's own terms ("archived", "written to the log") and shows no status field, in the event log and on the event's page, through the one shared delivery renderer from #465.httpandslackattempts are unchanged.Model: opus-5-5
#484: in the event log and on an event's page, a successful
databaseattempt now reads "archived" and a successfullogattempt "written to the log", with no status shown;httpandslackattempts are unchanged. The change is in the one shared attempt template, with one test per target type.Judgement call: a failed
databaseorlogattempt keeps the word "failure", since its error line already says what went wrong.Model: opus-5-5