Recordsgolanggoogle.golang.org/genproto/googleapis/rpcfailure issue
Failure signature
PROJECT_COMPILE exit 1 ×1
<path> undefined: otelgrpc.WithPublicEndpoint
Evidence quality: complete · go/compiler · compiler-diagnostic · outer go run · First recorded: 2026-10-14 · Last seen: 2026-10-14
sha256:d2494a4e5dbf…
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-20251029180050-ab9386a59fda PASS 3 passing observations
- v0.0.0-20250728155136-f173205681a0 not measured
- v0.0.0-20250707201910-8d1bb00bc6a7 not measured
- v0.0.0-20250519155744-55703ea1f237 FAIL
- v0.0.0-20250218202821-56aae31c358a PASS 1 passing observations
- v0.0.0-20250115164207-1a7da9e5054f PASS 1 passing observations
- v0.0.0-20241007155032-5fefd90f89a9 not measured
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-10-14 → 2026-10-14
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-20250218202821-56aae31c358a → first failing release v0.0.0-20250519155744-55703ea1f237
What differs across the boundary
- google.golang.org/protobuf v1.36.5 → v1.36.6 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-20250519155744-55703ea1f237 → first passing release v0.0.0-20251029180050-ab9386a59fda
Releases between them never measured at this stage: 2
What differs across the boundary
- google.golang.org/protobuf v1.36.10, v1.36.11, v1.36.12 → v1.36.6 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.0.0-20251029180050-ab9386a59fda | v0.0.0-20250728155136-f173205681a0 | v0.0.0-20250707201910-8d1bb00bc6a7 | v0.0.0-20250519155744-55703ea1f237 | v0.0.0-20250218202821-56aae31c358a | v0.0.0-20250115164207-1a7da9e5054f | v0.0.0-20241007155032-5fefd90f89a9 |
|---|---|---|---|---|---|---|---|
| google.golang.org/protobuf | v1.36.12 | v1.36.12 | v1.36.6 | v1.36.6 | v1.36.5 | v1.36.5 | v1.35.1 |
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: 3
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.