Recordsgolanggithub.com/munnerz/goautonegfailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×1
assertion 1 failed: expected text/plain; version=0.0.4; charset=utf-8, got text/plain; version=0.0.4; charset=utf-8; escaping=underscores · exit status 1
Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-09-05 · Last seen: 2026-09-05
sha256:69ab38336834…
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.
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×1 2026-09-05 → 2026-09-05
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.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/munnerz/goautoneg v0.0.0-20191010083416-a7dc8b61c822: negotiate HTTP Accept header content type using goautoneg 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. HOWNegotiateParseAccept MIT-0 · 2026-08-28