Recordsgolanggoogle.golang.org/grpcfailure 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…
google.golang.org/grpc.DialOption google.golang.org/grpc.WithTransportCredentials google.golang.org/grpc.WithUserAgent google.golang.org/grpc/credentials/insecure.NewCredentials
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.83.2 FAIL
- v1.83.1 not measured
- v1.83.0 not measured
- v1.83.0-dev not measured
- v1.80.0 PASS 5 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 v1.80.0 → first failing release v1.83.2
Releases between them never measured at this stage: 4
What differs across the boundary
- cloud.google.com/go/auth — → v0.18.2 hypothesis
- cloud.google.com/go/compute/metadata — → v0.9.0 hypothesis
- github.com/cncf/xds/go v0.0.0-20251210132809-ee656c7534f5 → v0.0.0-20260202195803-dba9d589def2 hypothesis
- github.com/envoyproxy/go-control-plane/envoy v1.36.0 → v1.37.0 hypothesis
- github.com/spiffe/go-spiffe/v2 v2.6.0 → v2.7.0 hypothesis
- go.opentelemetry.io/contrib/detectors/gcp v1.39.0 → v1.44.0 hypothesis
- go.opentelemetry.io/otel v1.43.0 → v1.46.0 hypothesis
- go.opentelemetry.io/otel/metric v1.43.0 → v1.46.0 hypothesis
- go.opentelemetry.io/otel/sdk v1.43.0 → v1.46.0 hypothesis
- go.opentelemetry.io/otel/sdk/metric v1.43.0 → v1.46.0 hypothesis
- go.opentelemetry.io/otel/trace v1.43.0 → v1.46.0 hypothesis
- golang.org/x/net v0.52.0 → v0.58.0 hypothesis
- golang.org/x/oauth2 v0.35.0 → v0.36.0 hypothesis
- golang.org/x/sync v0.20.0 → v0.22.0 hypothesis
- golang.org/x/sys v0.42.0 → v0.47.0 hypothesis
- google.golang.org/genproto/googleapis/rpc v0.0.0-20260401024825-9d38bb4040a9, v0.0.0-20260406210006-6f92a3bedf2d → v0.0.0-20260825221802-da73d73af1c5 hypothesis
- 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.
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: 9
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.