Records/golang/github.com/jackc/chunkreader/v2/failure issue

Where it was measured

PASS means the release recorded a passing observation at UNKNOWN and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.

• v2.0.1 FAIL
• v2.0.0 not measured

Where it reproduced

• os=linux · runtime=go@1.26 ×1 2026-10-09 → 2026-10-09

Nearest known PASS/FAIL boundaries

No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.

Evidence gaps

• The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
• The captured output could not establish: stage-unknown.
• No release in this window recorded a passing observation at UNKNOWN.
• Releases in this window never measured at UNKNOWN: 1
• No failure domain was inferred for this failure.

Published answers for the affected releases

• github.com/jackc/chunkreader/v2 v2.0.1: chunkreader.New Built ? 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 Built ? 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 Built ? 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