The event log at /hook/{id}/events now loads only the 50 newest events, limited in its query, and only the newest starts expanded; the rest start collapsed. Expanding and collapsing work as #471 left them. The 50 is recentEventLimit, the constant the recent events on a webhook's page already use.
Paging is removed rather than capped: with 50 events at most there is never a second page. That takes the Previous and Next links, the page query parameter, the page number that Replay and Resubmit carried back to the log, and pageOrFirst with its test. A ?page= left in an old link is ignored and shows the 50 newest, so the page-past-the-end problem in #349 (comment) goes with it.
When a webhook has more than 50 events, the count beside the heading reads "50 most recent of N events"; otherwise it still reads "N total events".
The comments in the access log middleware and the Sentry header filter, and a README line, said page was the only query parameter the service reads; they now name next and notice, which it already read.
The browser test now expects the newest event to start expanded: Enter collapses it and Space expands it, and the selection check scrolls the last event into view first, since the expanded newest event can push it below the short window.
Judgement call: the "50 most recent of N events" wording.
Left alone: three login tests still use /hook/abc/events?page=2 as a sample URL; they check that any query survives login.
static/css/tailwind.css is regenerated with make css.
Model: opus-5-5
The event log at `/hook/{id}/events` now loads only the 50 newest events, limited in its query, and only the newest starts expanded; the rest start collapsed. Expanding and collapsing work as https://git.eeqj.de/sneak/webhooker/pulls/471 left them. The 50 is `recentEventLimit`, the constant the recent events on a webhook's page already use.
Paging is removed rather than capped: with 50 events at most there is never a second page. That takes the Previous and Next links, the `page` query parameter, the page number that Replay and Resubmit carried back to the log, and `pageOrFirst` with its test. A `?page=` left in an old link is ignored and shows the 50 newest, so the page-past-the-end problem in https://git.eeqj.de/sneak/webhooker/issues/349#issuecomment-108756 goes with it.
When a webhook has more than 50 events, the count beside the heading reads "50 most recent of N events"; otherwise it still reads "N total events".
The comments in the access log middleware and the Sentry header filter, and a README line, said `page` was the only query parameter the service reads; they now name `next` and `notice`, which it already read.
The browser test now expects the newest event to start expanded: Enter collapses it and Space expands it, and the selection check scrolls the last event into view first, since the expanded newest event can push it below the short window.
- Judgement call: the "50 most recent of N events" wording.
- Left alone: three login tests still use `/hook/abc/events?page=2` as a sample URL; they check that any query survives login.
- `static/css/tailwind.css` is regenerated with `make css`.
Model: opus-5-5
The event log now loads the 50 newest events in its query and opens
only the newest on load, as the recent events on a webhook's page
already do. With 50 at most there is never a second page, so paging is
gone: the page links, the `page` query parameter, the page number that
Replay and Resubmit carried back to the log, and `pageOrFirst` with its
test. The count beside the heading reads "50 most recent of N events"
when there are more. The comments and README lines that named `page` as
the query parameter the service reads now name `next` and `notice`.
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.
The event log at
/hook/{id}/eventsnow loads only the 50 newest events, limited in its query, and only the newest starts expanded; the rest start collapsed. Expanding and collapsing work as #471 left them. The 50 isrecentEventLimit, the constant the recent events on a webhook's page already use.Paging is removed rather than capped: with 50 events at most there is never a second page. That takes the Previous and Next links, the
pagequery parameter, the page number that Replay and Resubmit carried back to the log, andpageOrFirstwith its test. A?page=left in an old link is ignored and shows the 50 newest, so the page-past-the-end problem in #349 (comment) goes with it.When a webhook has more than 50 events, the count beside the heading reads "50 most recent of N events"; otherwise it still reads "N total events".
The comments in the access log middleware and the Sentry header filter, and a README line, said
pagewas the only query parameter the service reads; they now namenextandnotice, which it already read.The browser test now expects the newest event to start expanded: Enter collapses it and Space expands it, and the selection check scrolls the last event into view first, since the expanded newest event can push it below the short window.
/hook/abc/events?page=2as a sample URL; they check that any query survives login.static/css/tailwind.cssis regenerated withmake css.Model: opus-5-5
clawbot referenced this pull request2026-10-03 03:31:03 +02:00
Review passed: this meets #349 on current
next.Model: opus-5-5
clawbot referenced this pull request2026-10-03 04:11:19 +02:00