Found while fixing #298 (its worker's report, on #302): answers that rproxy gives itself, such as a refusal, fail the same way when the visitor stops sending its body. With SWRP_MAX_REQUEST_TIME_MS=15000 and SWRP_MAX_RESPONSE_TIME_MS=300, the visitor got no bytes after 15 seconds. Start after that PR lands.
Definition of done, one PR into next, in internal/rproxy:
An answer rproxy gives itself while the visitor's body has not arrived whole reaches the visitor, in the same way that PR makes the app's answer reach it; a test fails without the change.
SPEC.md says what such a visitor gets.
make fmt, then flock -w 1800 /srv/code/tmp/.gate-smallwebwaf.lock make check passes. Label the PR needs-review.
Model: opus-5-5
Found while fixing https://git.eeqj.de/sneak/smallwebwaf/issues/298 (its worker's report, on https://git.eeqj.de/sneak/smallwebwaf/pulls/302): answers that `rproxy` gives itself, such as a refusal, fail the same way when the visitor stops sending its body. With `SWRP_MAX_REQUEST_TIME_MS=15000` and `SWRP_MAX_RESPONSE_TIME_MS=300`, the visitor got no bytes after 15 seconds. Start after that PR lands.
**Definition of done**, one PR into `next`, in `internal/rproxy`:
- An answer `rproxy` gives itself while the visitor's body has not arrived whole reaches the visitor, in the same way that PR makes the app's answer reach it; a test fails without the change.
- `SPEC.md` says what such a visitor gets.
- `make fmt`, then `flock -w 1800 /srv/code/tmp/.gate-smallwebwaf.lock make check` passes. Label the PR `needs-review`.
Model: opus-5-5
clawbot
self-assigned this 2026-11-10 20:59:33 +01:00
Plan.#302 has landed. Work in internal/rproxy and its tests: an answer rproxy gives itself while the visitor's body has not arrived whole goes out the same way that PR makes the app's answer go out, with Connection: close and the transport's read of the body ended. A test fails without the change, under the same settings that PR's tests use. Repeated runs of one test while finding out are the one exception to AGENTS.md's rule of checks only through make targets, and are not committed. make fmt, then flock -w 1800 /srv/code/tmp/.gate-smallwebwaf.lock make check; a flock timeout also exits 1, so read the output; at a load average far above 48, a timeout-only failure is reported as such, not fixed by lengthening anything. Push over SSH, since GITEA_TOKEN is refused. Start no subagent on another model. Title ending (closes #303).
Model: opus-5-5
**Plan.** https://git.eeqj.de/sneak/smallwebwaf/pulls/302 has landed. Work in `internal/rproxy` and its tests: an answer `rproxy` gives itself while the visitor's body has not arrived whole goes out the same way that PR makes the app's answer go out, with `Connection: close` and the transport's read of the body ended. A test fails without the change, under the same settings that PR's tests use. Repeated runs of one test while finding out are the one exception to `AGENTS.md`'s rule of checks only through `make` targets, and are not committed. `make fmt`, then `flock -w 1800 /srv/code/tmp/.gate-smallwebwaf.lock make check`; a `flock` timeout also exits 1, so read the output; at a load average far above 48, a timeout-only failure is reported as such, not fixed by lengthening anything. Push over SSH, since `GITEA_TOKEN` is refused. Start no subagent on another model. Title ending ` (closes #303)`.
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.
Found while fixing #298 (its worker's report, on #302): answers that
rproxygives itself, such as a refusal, fail the same way when the visitor stops sending its body. WithSWRP_MAX_REQUEST_TIME_MS=15000andSWRP_MAX_RESPONSE_TIME_MS=300, the visitor got no bytes after 15 seconds. Start after that PR lands.Definition of done, one PR into
next, ininternal/rproxy:rproxygives itself while the visitor's body has not arrived whole reaches the visitor, in the same way that PR makes the app's answer reach it; a test fails without the change.SPEC.mdsays what such a visitor gets.make fmt, thenflock -w 1800 /srv/code/tmp/.gate-smallwebwaf.lock make checkpasses. Label the PRneeds-review.Model: opus-5-5
Plan. #302 has landed. Work in
internal/rproxyand its tests: an answerrproxygives itself while the visitor's body has not arrived whole goes out the same way that PR makes the app's answer go out, withConnection: closeand the transport's read of the body ended. A test fails without the change, under the same settings that PR's tests use. Repeated runs of one test while finding out are the one exception toAGENTS.md's rule of checks only throughmaketargets, and are not committed.make fmt, thenflock -w 1800 /srv/code/tmp/.gate-smallwebwaf.lock make check; aflocktimeout also exits 1, so read the output; at a load average far above 48, a timeout-only failure is reported as such, not fixed by lengthening anything. Push over SSH, sinceGITEA_TOKENis refused. Start no subagent on another model. Title ending(closes #303).Model: opus-5-5