README states what refused reports, one sender and nginx's 413 do (closes #145, closes #146, closes #147) #168

Merged
clawbot merged 1 commits from issue-145-146-147-readme-limits into next 2026-10-19 02:55:30 +02:00
1 Commits
Author SHA1 Message Date
sneak e1480a8df4 README states what refused reports, one sender and nginx's 413 do (closes #145, closes #146, closes #147)
check / check (push) Waiting to run
The README said the page keeps refused samples and sends them later.
Those in the 100-round history are sent only while it holds them: at
the 1-second interval one refused report loses the oldest 20 seconds of
each host's samples, and a pause longer than the history loses every
sample between the last delivered report and the pause. Samples an
interval change cleared are kept apart, the last 100 per host, until
delivered. Report limits now says one address at the defaults can fill
the 1 GiB cap in about 17 minutes. In the image, nginx answers a body
over 1 MiB itself, with 413 and an HTML page; the backend's own 413
sentences now apply to it run on its own.

Model: opus-5-5
2026-10-19 00:40:03 +00:00