Recordsgolanggoogle.golang.org/grpcfailure 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.
- v1.58.1 not measured
- v1.40.0 PASS 4 passing observations
- v1.39.1 FAIL
- v1.37.0 not measured
- v1.36.0 PASS 1 passing observations
- v1.23.0 not measured
- v1.21.1 PASS 2 passing observations
- v1.20.1 FAIL
- v1.19.0 PASS 1 passing observations
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 passing release v1.19.0 → first failing release v1.20.1
What differs across the boundary
- github.com/golang/protobuf v1.2.0, v1.3.1, v1.3.2 → v1.3.1 hypothesis
- golang.org/x/lint v0.0.0-20181026193005-c67002cb31c3, v0.0.0-20190227174305-5b3e6a55c961 → v0.0.0-20190313153728-d0100b6bd8b3, v0.0.0-20190409202823-959b441ac422 hypothesis
- golang.org/x/net v0.0.0-20180826012351-8a410e7b638d, v0.0.0-20190213061140-3a22650c66bd, v0.0.0-20190313220215-9f648a60d977 → v0.0.0-20190311183353-d8887717615a, v0.0.0-20190503192946-f4e77d36d62c hypothesis
- golang.org/x/oauth2 v0.0.0-20180821212333-d2e6202438be, v0.0.0-20181203162652-d668ce993890, v0.0.0-20190226205417-e64efc72b421 → v0.0.0-20190226205417-e64efc72b421, v0.0.0-20190604053449-0f29369cfe45 hypothesis
- golang.org/x/sys v0.0.0-20180830151530-49385e6e1522, v0.0.0-20181029174526-d69651ed3497, v0.0.0-20190316082340-a2f829d7f35f → v0.0.0-20190215142949-d0b11bdaac8a, v0.0.0-20190507160741-ecd444e8653b hypothesis
- golang.org/x/tools v0.0.0-20190114222345-bf090417da8b, v0.0.0-20190226205152-f727befe758c → v0.0.0-20190312170243-e65039ee4138, v0.0.0-20190506145303-2d16b83fe98c hypothesis
- google.golang.org/genproto v0.0.0-20180817151627-c66870c02cf8, v0.0.0-20190306203927-b5d61aea6440, v0.0.0-20190911173649-1774047e7e51, v0.0.0-20191108220845-16a3f7862a1a → v0.0.0-20190307195333-5fe7a883aa19, v0.0.0-20190502173448-54afdca5d873 hypothesis
- honnef.co/go/tools v0.0.0-20190102054323-c2f93a96b099, v0.0.0-20190106161140-3f1c8253044a → v0.0.0-20190102054323-c2f93a96b099, v0.0.0-20190418001031-e561f6794a2a 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 v1.20.1 → first passing release v1.21.1
What differs across the boundary
- github.com/golang/mock v1.3.1 → v1.1.1, v1.2.0 hypothesis
- github.com/golang/protobuf v1.3.2 → v1.3.1 hypothesis
- github.com/google/go-cmp v0.3.0 → — hypothesis
- golang.org/x/lint v0.0.0-20190409202823-959b441ac422, v0.0.0-20190909230951-414d861bb4ac, v0.0.0-20190930215403-16217165b5de → v0.0.0-20190313153728-d0100b6bd8b3, v0.0.0-20190409202823-959b441ac422 hypothesis
- golang.org/x/net v0.0.0-20190620200207-3b0461eec859 → v0.0.0-20190311183353-d8887717615a, v0.0.0-20190503192946-f4e77d36d62c hypothesis
- golang.org/x/oauth2 v0.0.0-20190604053449-0f29369cfe45 → v0.0.0-20190226205417-e64efc72b421, v0.0.0-20190604053449-0f29369cfe45 hypothesis
- golang.org/x/sys v0.0.0-20190624142023-c5567b49c5d0 → v0.0.0-20190215142949-d0b11bdaac8a, v0.0.0-20190507160741-ecd444e8653b hypothesis
- golang.org/x/tools v0.0.0-20190628153133-6cdbf07be9d0, v0.0.0-20190911174233-4f2ddba30aff, v0.0.0-20191112195655-aa38f8e97acc, v0.0.0-20191113191852-77e3bb0ad9e7, v0.0.0-20191115202509-3a792d9c32b2 → v0.0.0-20190312170243-e65039ee4138, v0.0.0-20190506145303-2d16b83fe98c hypothesis
- google.golang.org/genproto v0.0.0-20190801165951-fa694d86fc64, v0.0.0-20190819201941-24fa4b261c55, v0.0.0-20190911173649-1774047e7e51, v0.0.0-20191108220845-16a3f7862a1a, v0.0.0-20191115194625-c23dd37a84c9 → v0.0.0-20190307195333-5fe7a883aa19, v0.0.0-20190502173448-54afdca5d873 hypothesis
- honnef.co/go/tools v0.0.0-20190418001031-e561f6794a2a, v0.0.1-2019.2.3 → v0.0.0-20190102054323-c2f93a96b099, v0.0.0-20190418001031-e561f6794a2a 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 v1.36.0 → first failing release v1.39.1
Releases between them never measured at this stage: 1
What differs across the boundary
- github.com/envoyproxy/go-control-plane v0.9.9-0.20201210154907-fd9021fe5dad, v0.9.9-0.20210512163311-63b5d3c536b0 → v0.9.9-0.20210512163311-63b5d3c536b0 hypothesis
- github.com/golang/protobuf v1.4.3 → v1.5.2 hypothesis
- github.com/google/go-cmp v0.5.0 → v0.5.6 hypothesis
- golang.org/x/net v0.0.0-20200822124328-c89045814202 → v0.0.0-20210503060351-7fd8e65b6420 hypothesis
- golang.org/x/oauth2 v0.0.0-20200107190931-bf48bf16ab8d → v0.0.0-20210805134026-6f1e6394065a hypothesis
- golang.org/x/sys v0.0.0-20200323222414-85ca7c5b95cd → v0.0.0-20210806184541-e5e7981a1069 hypothesis
- google.golang.org/genproto v0.0.0-20200526211855-cb27e3aa2013 → v0.0.0-20210805201207-89edb61ffb67, v0.0.0-20210813162853-db860fec028c hypothesis
- google.golang.org/protobuf v1.25.0 → v1.27.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 failing release v1.39.1 → first passing release v1.40.0
What differs across the boundary
- github.com/cespare/xxhash v1.1.0 → — hypothesis
- github.com/golang/protobuf v1.4.3, v1.5.2 → v1.5.2 hypothesis
- github.com/google/go-cmp v0.5.0, v0.5.5, v0.5.6, v0.5.9 → v0.5.6 hypothesis
- golang.org/x/net v0.0.0-20200822124328-c89045814202, v0.0.0-20210405180319-a5a99cb37ef4, v0.0.0-20210503060351-7fd8e65b6420, v0.0.0-20211112202133-69e39bad7dc2 → v0.0.0-20210503060351-7fd8e65b6420 hypothesis
- golang.org/x/oauth2 v0.0.0-20200107190931-bf48bf16ab8d, v0.0.0-20210805134026-6f1e6394065a → v0.0.0-20210805134026-6f1e6394065a hypothesis
- golang.org/x/sys v0.0.0-20200323222414-85ca7c5b95cd, v0.0.0-20210510120138-977fb7262007, v0.0.0-20210806184541-e5e7981a1069, v0.8.0, v0.9.0 → v0.0.0-20210806184541-e5e7981a1069 hypothesis
- google.golang.org/genproto v0.0.0-20200526211855-cb27e3aa2013, v0.0.0-20210821163610-241b8fcbd6c8 → v0.0.0-20210805201207-89edb61ffb67, v0.0.0-20210813162853-db860fec028c hypothesis
- google.golang.org/protobuf v1.25.0, v1.27.1, v1.28.0 → v1.27.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.
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.
Moved: 15 · unchanged at every release: 6
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: 3
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.