Recordsgolanggolang.org/x/oauth2failure issue
Failure signature
PROJECT_COMPILE exit 1 ×2
test/contract.go:<n>:<n>: cannot use <str> (untyped string constant) as *url.URL value in argument to googleapi.Expand
Evidence quality: complete · go/compiler · compiler-diagnostic · outer go run · First recorded: 2026-10-18 · Last seen: 2026-10-22
sha256:54d6a6669dcf…
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.36.0 PASS 4 passing observations
- v0.19.0 not measured
- v0.0.0-20220223155221-ee480838109b not measured
- v0.0.0-20210805134026-6f1e6394065a FAIL
- v0.0.0-20210514164344-f6687ab2804c not measured
- v0.0.0-20200107190931-bf48bf16ab8d PASS 1 passing observations
- v0.0.0-20191202225959-858c2ad4c8b6 PASS 1 passing observations
- v0.0.0-20190604053449-0f29369cfe45 FAIL
- v0.0.0-20190226205417-e64efc72b421 not measured
Where it reproduced
- os=linux · runtime=go@1.26 ×2 2026-10-18 → 2026-10-22
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 failing release v0.0.0-20190604053449-0f29369cfe45 → first passing release v0.0.0-20191202225959-858c2ad4c8b6
What differs across the boundary
- cloud.google.com/go v0.50.0 → v0.38.0, v0.44.1, v0.44.2, v0.45.1, v0.46.3 hypothesis
- golang.org/x/net v0.0.0-20191209160850-c0dbc17a3553 → v0.0.0-20190503192946-f4e77d36d62c, v0.0.0-20190620200207-3b0461eec859 hypothesis
- google.golang.org/appengine v1.6.5 → v1.5.0, v1.6.1 hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
-
Last passing release v0.0.0-20200107190931-bf48bf16ab8d → first failing release v0.0.0-20210805134026-6f1e6394065a
Releases between them never measured at this stage: 1
What differs across the boundary
- cloud.google.com/go v0.34.0, v0.52.0, v0.56.0, v0.57.0, v0.62.0, v0.65.0 → v0.90.0, v0.93.3 hypothesis
- golang.org/x/net v0.0.0-20200114155413-6afb5195e5aa, v0.0.0-20200202094626-16171245cfb2, v0.0.0-20200324143707-d3edc9973b7e, v0.0.0-20200520182314-0ba52f642ac2, v0.0.0-20200707034311-ab3426394381, v0.0.0-20200822124328-c89045814202, v0.0.0-20210405180319-a5a99cb37ef4 → v0.0.0-20210503060351-7fd8e65b6420, v0.0.0-20211112202133-69e39bad7dc2 hypothesis
- google.golang.org/appengine v1.4.0, v1.6.5, v1.6.6 → v1.6.7 hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
-
Last failing release v0.0.0-20210805134026-6f1e6394065a → first passing release v0.36.0
Releases between them never measured at this stage: 3
What differs across the boundary
- cloud.google.com/go — → v0.90.0, v0.93.3 hypothesis
- cloud.google.com/go/compute/metadata v0.9.0 → — hypothesis
- golang.org/x/net — → v0.0.0-20210503060351-7fd8e65b6420, v0.0.0-20211112202133-69e39bad7dc2 hypothesis
- google.golang.org/appengine — → v1.6.7 hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
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.36.0 | v0.19.0 | v0.0.0-20220223155221-ee480838109b | v0.0.0-20210805134026-6f1e6394065a | v0.0.0-20210514164344-f6687ab2804c | v0.0.0-20200107190931-bf48bf16ab8d | v0.0.0-20191202225959-858c2ad4c8b6 | v0.0.0-20190604053449-0f29369cfe45 | v0.0.0-20190226205417-e64efc72b421 |
|---|---|---|---|---|---|---|---|---|---|
| cloud.google.com/go | — | — | v0.65.0 | v0.90.0 | v0.65.0 | v0.65.0 | v0.50.0 | v0.45.1 | v0.37.0 |
| cloud.google.com/go/compute/metadata | v0.9.0 | v0.3.0 | — | — | — | — | — | — | — |
| golang.org/x/net | — | — | v0.4.0 | v0.0.0-20211112202133-69e39bad7dc2 | v0.0.0-20210525063256-abc453219eb5 | v0.0.0-20200520182314-0ba52f642ac2 | v0.0.0-20191209160850-c0dbc17a3553 | v0.0.0-20190503192946-f4e77d36d62c | v0.0.0-20190311183353-d8887717615a |
| google.golang.org/appengine | — | — | — | v1.6.7 | v1.6.6 | v1.6.6 | v1.6.5 | v1.5.0 | v1.4.0 |
| github.com/google/go-cmp | — | v0.6.0 | — | — | — | — | — | — | — |
Moved: 4 · unchanged at every release: 1
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
- Releases in this window never measured at PROJECT_COMPILE: 4
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.