Recordsgolanggithub.com/jackc/chunkreader/v2failure issue
Failure signature
PROJECT_COMPILE exit 1 ×1
<path>:<n>:<n>: too many arguments in call to c.conn.Write · <path>:<n>:<n>: too many arguments in call to c.conn.Write …
Evidence quality: complete · go/compiler · compiler-diagnostic · outer go run · First recorded: 2026-09-20 · Last seen: 2026-09-20
sha256:417d6d04e560…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_COMPILE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-09-20 → 2026-09-20
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last passing release v2.0.0 → first failing release v2.0.1
Both trees resolved every dependency to the same version. Nothing here moved.
Evidence gaps
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/jackc/chunkreader/v2 v2.0.1: chunkreader.New This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWchunkreader.Newgo 1.26.6 MIT-0 · 2026-08-26
- github.com/jackc/chunkreader/v2 v2.0.1: chunkreader.ChunkReader.Next This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWchunkreader.ChunkReader.Next MIT-0 · 2026-08-26
- github.com/jackc/chunkreader/v2 v2.0.1 This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOW MIT-0 · 2026-08-23