3 Commits

Include renames

Author	SHA1	Message	Date
clawbot	688cc11d38	Give each event its own page and show bodies the same everywhere (closes #369) ... Each row of the recent events on the webhook page links to the event's own page, /hook/{id}/events/{eventID}, and expands to show its body; only the newest starts expanded. The event's page shows its details, its whole body and every delivery with its attempts. One renderer, newBodyView with templates/event_body.html, shows a body in all three places: whole up to 32 KiB, cut there in the lists with a link to the event's page, JSON pretty-printed, a body of more than 200 lines or 32 KiB in a scrolling box, and a body that is not text left out beside its download link. A resubmitted copy links to its original's page. Model: opus-5-5	2026-10-02 19:50:45 +00:00
clawbot	89f3b984d2	Resubmit a stored event as a new undelivered event (closes #250)	2026-08-24 00:53:37 +02:00
clawbot	279effb4c2	Bound the event log's rendered bodies in the query (closes #135) ... The event log rendered stored bodies untruncated. Since buffered rendering landed (#123) that became resident memory per concurrent viewer, up to tens of MB, driven by payloads unauthenticated clients supply to the public receiver. Bound in the query rather than the template, via substr(cast(body as blob), 1, ?) plus length(cast(body as blob)), so an oversized body never becomes a Go string at all. Adds an EventLogView projection carrying the true byte count, and trims a partial UTF-8 tail without rewriting bodies that are merely invalid UTF-8. Independently reviewed. The generated SQL was dumped under GORM DryRun to confirm the cap is a bound parameter, both casts are present, and no other path selects the full column; soft-delete scope, ordering and pagination are unchanged. Correction to the PR body: its quoted mutation output was produced by removing the bound from eventLogColumns, not by raising the cap to 1<<30 as the text claimed. The reviewer reproduced the real mutation and confirmed the tests do catch removal of the bound. Follow-up #157 restores in-app retrieval of bodies above the cap.	2026-08-17 22:57:08 +02:00