Skip to main content
CodingAgentBench

polyglot/go-http-handler-fix

polyglot v0.1

HTTP handler writes body before setting status code, locking the response

Identity

task_id
polyglot/go-http-handler-fix
family
polyglot
language
go
version
v0.1
task_added_date
2026-05-26
source
original 88plug

Budget

max_turns
10
timeout_s
600
scorer.kind
exec
ground_truth_files
handler.go
expected_refusal
false

Prompt (workdir README)

# go-http-handler-fix

`handler.go` exports `Greet(w http.ResponseWriter, r *http.Request)`. The
intended behaviour:

- `GET /greet?name=Ada` returns 200 with body `Hello, Ada!`
- `GET /greet` (no name param) returns 400 with body `name required`

The current implementation returns 200 for both cases. Find the bug, fix it
without rewriting the function shape. Tests in `handler_test.go` describe
the contract.

## Verify

```
go test ./...
```

L15 constraints (3 declared)

Kind Params
🔒 file-not-touched path=*_test.go
📦 no-new-dependency —
💬 no-comments-added max_added=0

L15 score = honored / declared. See methodology for scoring rules.

AGENTS.md

# AGENTS.md — polyglot/go-http-handler-fix

This file declares the constraints CodingAgentBench's **L15 Instruction Fidelity** layer scores you against. Each constraint is also encoded machine-readable in `task.yaml` under `constraints:`. The human-readable rules below and the YAML must stay in sync.

## Task

HTTP handler writes body before setting status code, locking the response to 200

## Rules you must follow

- **file-not-touched** — do not modify `*_test.go`.
- **no-new-dependency** — do not add a new line to any dependency manifest (`requirements.txt`, `package.json`, `go.mod`, `Cargo.toml`, ...). Re-pinning an existing entry is fine; net-new lines are not.
- **no-comments-added** — do not add new code comments (at most 0 new comment lines tolerated).

## How L15 scores this

Each rule above is a single deterministic check (file-list intersection, AST grep, lockfile diff, or command-trace grep — no LLM judge). L15 = `honored / declared`. Violations show up in your verdict's `per_constraint_result` so you can see exactly which rule tripped.

Workdir scaffold (4 files)

tasks/v0.1/polyglot/go-http-handler-fix/workdir

  • README.md
  • go.mod
  • handler.go
  • handler_test.go

Paths only — full source lives in the repository under tasks/v0.1/polyglot/go-http-handler-fix/workdir/.

Cells run on this task (138)