Recordsgolanggoogle.golang.org/genprotofailure 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.
- v0.0.0-20190502173448-54afdca5d873 PASS 1 passing observations
- v0.0.0-20190307195333-5fe7a883aa19 not measured
- v0.0.0-20190306203927-b5d61aea6440 not measured
- v0.0.0-20181202183823-bd91e49a0898 not measured
- v0.0.0-20180817151627-c66870c02cf8 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 v0.0.0-20180817151627-c66870c02cf8 → first passing release v0.0.0-20190502173448-54afdca5d873
Releases between them never measured at this stage: 3
One side of this boundary has no resolved dependency tree, so nothing could be compared.
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.0.0-20190502173448-54afdca5d873 | v0.0.0-20190307195333-5fe7a883aa19 | v0.0.0-20190306203927-b5d61aea6440 | v0.0.0-20181202183823-bd91e49a0898 |
|---|---|---|---|---|
| github.com/golang/protobuf | v1.3.1 | v1.3.1 | v1.5.4 | v1.2.0 |
| golang.org/x/lint | v0.0.0-20190409202823-959b441ac422 | v0.0.0-20190313153728-d0100b6bd8b3 | v0.0.0-20190227174305-5b3e6a55c961 | — |
| golang.org/x/net | v0.0.0-20190503192946-f4e77d36d62c | v0.0.0-20190311183353-d8887717615a | v0.38.0 | v0.0.0-20181106065722-10aee1819953 |
| golang.org/x/tools | v0.0.0-20190506145303-2d16b83fe98c | v0.0.0-20190312170243-e65039ee4138 | v0.31.0 | — |
| google.golang.org/grpc | v1.20.1 | v1.20.1 | v1.67.1 | v1.17.0 |
| honnef.co/go/tools | v0.0.0-20190418001031-e561f6794a2a | v0.0.0-20190102054323-c2f93a96b099 | v0.0.0-20190102054323-c2f93a96b099 | — |
| golang.org/x/exp | v0.0.0-20190121172915-509febef88a4 | v0.0.0-20190121172915-509febef88a4 | v0.0.0-20190121172915-509febef88a4 | — |
Moved: 6 · 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: 3
- No resolved dependency tree for v0.0.0-20190502173448-54afdca5d873 or for v0.0.0-20180817151627-c66870c02cf8, so the versions either side of the boundary could not be compared.
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.