Recordsgolangmodernc.org/strutilfailure issue
Failure signature
UNKNOWN exit 1 EOF Evidence gap ×1
Assertion 2 failed: unexpected error on empty input: EOF · exit status 1
Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-09-16 · Last seen: 2026-09-16
sha256:9c4b09afd564…
modernc.org/strutil.Base64Decode modernc.org/strutil.Base64Encode
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.
- v1.2.1 FAIL
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-09-16 → 2026-09-16
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
- modernc.org/strutil v1.2.1: Base64Decode 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. HOWmodernc.org/strutil.Base64Decode MIT-0 · 2026-09-19
- modernc.org/strutil v1.2.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. HOWgo 1.26.6 MIT-0 · 2026-09-16