Recordsgolanggolang.org/x/modfailure issue
Failure signature
PROJECT_RESOLVE exit 1 ×2
<path> missing go.sum entry for module providing package golang.org/x/xerrors (imported by golang.org/x/mod/module); to add:
Evidence quality: complete · go/module · resolve-diagnostic · outer go run · First recorded: 2026-09-19 · Last seen: 2026-09-20
sha256:cbb2a2f7b0fd…
golang.org/x/mod/module.Check golang.org/x/mod/module.InvalidVersionError golang.org/x/mod/module.ModuleError golang.org/x/mod/module.Version golang.org/x/mod/module.VersionError
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.
- v0.3.0 not measured
- v0.2.0 not measured
- v0.1.1-0.20191107180719-034126e5016b not measured
- v0.1.1-0.20191105210325-c90efee705ee FAIL
- v0.1.0 not measured
- v0.0.0-20190513183733-4bf6d317e70e not measured
Where it reproduced
- os=linux · runtime=go@1.26 ×2 2026-09-19 → 2026-09-20
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.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
| Library | v0.3.0 | v0.2.0 | v0.1.1-0.20191107180719-034126e5016b | v0.1.1-0.20191105210325-c90efee705ee | v0.1.0 | v0.0.0-20190513183733-4bf6d317e70e |
|---|---|---|---|---|---|---|
| golang.org/x/crypto | v0.0.0-20191011191535-87dc89f01550 | v0.0.0-20191011191535-87dc89f01550 | v0.0.0-20191011191535-87dc89f01550 | v0.0.0-20210711020723-a769d52b0f97 | v0.0.0-20190510104115-cbcb75029529 | v0.0.0-20190510104115-cbcb75029529 |
| golang.org/x/tools | v0.0.0-20200618134242-20370b0cb4b2 | v0.0.0-20200331025713-a30bf2db82d4 | — | — | — | — |
| golang.org/x/xerrors | v0.0.0-20200804184101-5ec99f83aff1 | v0.0.0-20191204190536-9bdfabe68543 | v0.0.0-20191011141410-1b5146add898 | v0.0.0-20191204190536-9bdfabe68543 | — | — |
Moved: 3 · unchanged at every release: 0
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.
Evidence gaps
- No release in this window recorded a passing observation at PROJECT_RESOLVE.
- Releases in this window never measured at PROJECT_RESOLVE: 5
- No failure domain was inferred for this failure.
Published answers for the affected releases
- golang.org/x/mod v0.1.1-0.20191105210325-c90efee705ee: module.ModuleError 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. HOWgolang.org/x/mod/module.ModuleError MIT-0 · 2026-09-20
- golang.org/x/mod v0.1.1-0.20191105210325-c90efee705ee: module.Check 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. HOWgolang.org/x/mod/module.Check MIT-0 · 2026-09-20
- golang.org/x/mod v0.1.1-0.20191105210325-c90efee705ee: module.Check 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. HOWmodule.Check MIT-0 · 2026-09-18