Recordsgolanggoogle.golang.org/grpcfailure issue
Failure signature
PROJECT_COMPILE exit 1 ×1
test/contract.go:<n>:<n>: undefined: gax.WithPath
Evidence quality: complete · go/compiler · compiler-diagnostic · outer go run · First recorded: 2026-10-21 · Last seen: 2026-10-21
sha256:5d8a7576dab3…
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.20.1 PASS 1 passing observations
- v1.19.0 PASS 1 passing observations
- v1.17.0 not measured
- v1.16.0 FAIL
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-10-21 → 2026-10-21
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 v1.16.0 → first passing release v1.19.0
Releases between them never measured at this stage: 1
What differs across the boundary
- github.com/golang/lint — → v0.0.0-20180702182130-06c8688daad7 hypothesis
- github.com/golang/mock v1.1.1, v1.2.0 → v1.1.1 hypothesis
- github.com/golang/protobuf v1.2.0, v1.3.1, v1.3.2 → v1.2.0 hypothesis
- golang.org/x/lint v0.0.0-20181026193005-c67002cb31c3, v0.0.0-20190227174305-5b3e6a55c961 → — hypothesis
- golang.org/x/net v0.0.0-20180826012351-8a410e7b638d, v0.0.0-20190213061140-3a22650c66bd, v0.0.0-20190313220215-9f648a60d977 → v0.0.0-20180826012351-8a410e7b638d, v0.0.0-20181029044818-c44066c5c816 hypothesis
- golang.org/x/oauth2 v0.0.0-20180821212333-d2e6202438be, v0.0.0-20181203162652-d668ce993890, v0.0.0-20190226205417-e64efc72b421 → v0.0.0-20180821212333-d2e6202438be, v0.0.0-20181017192945-9dcd33a902f4 hypothesis
- golang.org/x/sys v0.0.0-20180830151530-49385e6e1522, v0.0.0-20181029174526-d69651ed3497, v0.0.0-20190316082340-a2f829d7f35f → v0.0.0-20180830151530-49385e6e1522, v0.0.0-20181029174526-d69651ed3497 hypothesis
- golang.org/x/tools v0.0.0-20190114222345-bf090417da8b, v0.0.0-20190226205152-f727befe758c → v0.0.0-20180828015842-6cd1fcedba52, v0.0.0-20181030000716-a0a13e073c7b 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-20180817151627-c66870c02cf8, v0.0.0-20181029155118-b69ba1387ce2 hypothesis
- honnef.co/go/tools v0.0.0-20190102054323-c2f93a96b099, v0.0.0-20190106161140-3f1c8253044a → v0.0.0-20180728063816-88497007e858 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: 9 · unchanged at every release: 3
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: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.