Recordsgolanggolang.org/x/xerrorsfailure issue
Failure signature
PROJECT_COMPILE exit 1 ×1
<path> undefined: config.NewConfig
Evidence quality: complete · go/compiler · compiler-diagnostic · outer go run · First recorded: 2026-08-31 · Last seen: 2026-08-31
sha256:0a43185f3587…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_COMPILE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- v0.0.0-20200804184101-5ec99f83aff1 FAIL
- v0.0.0-20191204190536-9bdfabe68543 not measured
- v0.0.0-20191011141410-1b5146add898 PASS 1 passing observations
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-08-31 → 2026-08-31
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-20191011141410-1b5146add898 → first failing release v0.0.0-20200804184101-5ec99f83aff1
Releases between them never measured at this stage: 1
One side of this boundary has no resolved dependency tree, so nothing could be compared.
Evidence gaps
- Releases in this window never measured at PROJECT_COMPILE: 1
- No resolved dependency tree for v0.0.0-20191011141410-1b5146add898 or for v0.0.0-20200804184101-5ec99f83aff1, 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/xerrors v0.0.0-20200804184101-5ec99f83aff1: xerrors error wrapping and chain inspection with Errorf and Is 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. HOWxerrors.Errorfxerrors.Is MIT-0 · 2026-08-27