Recordsgolanggolang.org/x/syncfailure issue
Failure signature
PROJECT_PROCESS Evidence gap ×1
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-26 · Last seen: 2026-08-26
Where it was measured
PASS means the release recorded a passing observation at PROJECT_PROCESS and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- v0.20.0 PASS 44 passing observations
- v0.19.0 PASS 8 passing observations
- v0.17.0 PASS 1 passing observations
- v0.12.0 FAIL
- v0.8.0 not measured
- v0.7.0 not measured
- v0.0.0-20200625203802-6e8e738ad208 PASS 8 passing observations
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-08-26 → 2026-08-26
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last passing release v0.0.0-20200625203802-6e8e738ad208 → first failing release v0.12.0
Releases between them never measured at this stage: 2
One side of this boundary has no resolved dependency tree, so nothing could be compared.
-
Last failing release v0.12.0 → first passing release v0.17.0
One side of this boundary has no resolved dependency tree, so nothing could be compared.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- Releases in this window never measured at PROJECT_PROCESS: 2
- No resolved dependency tree for v0.0.0-20200625203802-6e8e738ad208 or for v0.12.0, so the versions either side of the boundary could not be compared.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- golang.org/x/sync v0.12.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