Recordsgolanggoogle.golang.org/genproto/googleapis/rpcfailure issue
Failure signature
PROJECT_COMPILE exit 1 ×1
<path>:<n>:<n>: undefined: api.KeyValue · <path>:<n>:<n>: undefined: api.KeyValue · <path>:<n>:<n>: undefined: api.KeyValue …
Evidence quality: complete · go/compiler · compiler-diagnostic · outer go run · First recorded: 2026-09-07 · Last seen: 2026-09-07
sha256:6ffbd74e9935…
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-20260904194346-d0f1323225a4 PASS 3 passing observations
- v0.0.0-20260831171406-18b4a7587f8a not measured
- v0.0.0-20260825221802-da73d73af1c5 PASS 5 passing observations
- v0.0.0-20260819154853-08b0e4226688 FAIL
- v0.0.0-20260720211330-0afa2a65878a not measured
- v0.0.0-20260526163538-3dc84a4a5aaa not measured
- v0.0.0-20260427160629-7cedc36a6bc4 not measured
- v0.0.0-20260406210006-6f92a3bedf2d PASS 1 passing observations
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-09-07 → 2026-09-07
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 v0.0.0-20260406210006-6f92a3bedf2d → first failing release v0.0.0-20260819154853-08b0e4226688
Releases between them never measured at this stage: 3
What differs across the boundary
- google.golang.org/protobuf v1.36.11 → v1.36.12 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-20260819154853-08b0e4226688 → first passing release v0.0.0-20260825221802-da73d73af1c5
Both trees resolved every dependency to the same version. Nothing here moved.
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-20260904194346-d0f1323225a4 | v0.0.0-20260831171406-18b4a7587f8a | v0.0.0-20260825221802-da73d73af1c5 | v0.0.0-20260819154853-08b0e4226688 | v0.0.0-20260526163538-3dc84a4a5aaa | v0.0.0-20260427160629-7cedc36a6bc4 | v0.0.0-20260406210006-6f92a3bedf2d |
|---|---|---|---|---|---|---|---|
| google.golang.org/protobuf | v1.36.12 | v1.36.12 | v1.36.12 | v1.36.12 | v1.36.11 | v1.36.12 | v1.36.11 |
Moved: 1 · unchanged at every release: 0
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.