Recordsgolanggolang.org/x/oauth2failure 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.
- v0.19.0 not measured
- v0.0.0-20220223155221-ee480838109b not measured
- v0.0.0-20210514164344-f6687ab2804c not measured
- v0.0.0-20200107190931-bf48bf16ab8d FAIL
- v0.0.0-20190226205417-e64efc72b421 not measured
Where it reproduced
- os=linux · runtime=go@1.26 ×2 2026-09-19 → 2026-09-19
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.19.0 | v0.0.0-20220223155221-ee480838109b | v0.0.0-20210514164344-f6687ab2804c | v0.0.0-20200107190931-bf48bf16ab8d | v0.0.0-20190226205417-e64efc72b421 |
|---|---|---|---|---|---|
| cloud.google.com/go | — | v0.65.0 | v0.65.0 | v0.65.0 | v0.37.0 |
| golang.org/x/net | — | v0.4.0 | v0.0.0-20210525063256-abc453219eb5 | v0.0.0-20200822124328-c89045814202 | v0.0.0-20190313220215-9f648a60d977 |
| google.golang.org/appengine | — | — | v1.6.6 | v1.6.5 | v1.4.0 |
| cloud.google.com/go/compute/metadata | v0.3.0 | — | — | — | — |
| github.com/google/go-cmp | v0.6.0 | — | — | — | — |
Moved: 3 · unchanged at every release: 2
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: 4
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.