v1.1 plan: state the ReverseProxy abort behaviour the fix depends on; note the second stop
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
@@ -32,3 +32,11 @@ Branch `v1.1`. One task, one fresh OpenCode session, one commit.
|
||||
the sandbox refused a `/tmp` scratch program (the I9 pattern, third time tonight). The rule
|
||||
against ending a turn on a refusal lived only in v1's task 05; it is now in `AGENTS.md`, so every
|
||||
task carries it. Resumed from the working tree.
|
||||
- 2026-09-25, task 01, second session: two of three tests passing; the mid-stream cancel wrote
|
||||
no row because `httputil.ReverseProxy` does not return when the client disconnects mid-copy on a
|
||||
real server — it panics with `http.ErrAbortHandler`, so code after `rp.ServeHTTP` never runs.
|
||||
Ornith tried to read the Go source tree to find that out; the sandbox refused (outside the
|
||||
repository) and the session ended on the refusal again. Two faults: the task text did not state
|
||||
the environment's behaviour (mine — the customer describes the world the code runs in), and the
|
||||
model ended a turn on a refusal (its, fourth time). Third session given the fact and told to
|
||||
record from a deferred function with `recover()`.
|
||||
|
||||
Reference in New Issue
Block a user