CodeSampleX

Recordsgolanggolang.org/x/lintfailure issue

Failure signature

PROJECT_RESOLVE exit 1 ×2

test/contract.go:<n>:<n>: missing go.sum entry for module providing package cloud.google.com/go/storage (imported by example.com/sample/test); to add: …

Evidence quality: complete · go/module · resolve-diagnostic · outer go run · First recorded: 2026-09-19 · Last seen: 2026-09-19

sha256:960c448010d3…

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

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.

Libraryv0.0.0-20210508222113-6edffad5e616v0.0.0-20200302205851-738671d3881bv0.0.0-20200130185559-910be7a94367v0.0.0-20191125180803-fdd1cda4f05fv0.0.0-20190930215403-16217165b5de
golang.org/x/tools v0.0.0-20200130002326-2f3ba24bd6e7 v0.1.12 v0.0.0-20200204074204-1cc6d1ef6c74 v0.0.0-20200122220014-bf1340f18c4a v0.0.0-20191112195655-aa38f8e97acc

Moved: 1 · 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

Published answers for the affected releases

No published sample names these releases.

Back to the package