Recordsgolanggolang.org/x/syncfailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×1
FAIL: cached certs count 5 exceeded capacity 3 · exit status 1
Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-09-04 · Last seen: 2026-09-04
sha256:6ad787e54840…
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.
- v0.22.0 not measured
- v0.21.0 not measured
- v0.20.0 FAIL
- v0.19.0 not measured
- v0.17.0 not measured
- v0.12.0 not measured
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-09-04 → 2026-09-04
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: 5
- No failure domain was inferred for this failure.
Published answers for the affected releases
- golang.org/x/sync v0.20.0: errgroup.Group, errgroup.WithContext, singleflight.Group 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. HOWerrgroup.Grouperrgroup.WithContextsingleflight.Groupsemaphore.Weightedgo 1.26 MIT-0 · 2026-08-20
- golang.org/x/sync v0.20.0 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-19