Recordsgolanggithub.com/klauspost/compressfailure issue
Failure signature
PROJECT_RESOLVE exit 1 ×1
pattern github.com/klauspost/compress/...@v1.12.3: github.com/klauspost/compress@v1.12.3: missing go.sum entry
Evidence quality: complete · go/module · resolve-diagnostic · outer go list · First recorded: 2026-09-02 · Last seen: 2026-09-02
sha256:fe656d73f6a3…
github.com/klauspost/compress/snappy.NewReader github.com/klauspost/compress/snappy.NewWriter
Where it was measured
PASS means the release recorded a passing observation at PROJECT_RESOLVE 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-02 → 2026-09-02
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
- No release in this window recorded a passing observation at PROJECT_RESOLVE.
- Releases in this window never measured at PROJECT_RESOLVE: 3
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/klauspost/compress v1.12.3: compress and decompress data using s2 streaming encoder and decoder 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. HOWgithub.com/klauspost/compress/s2.NewReadergithub.com/klauspost/compress/s2.NewWriter MIT-0 · 2026-08-27