Records/golang/google.golang.org/grpc/failure issue

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.71.0 PASS 1 passing observations
• v1.67.1 not measured
• v1.63.2 not measured
• v1.58.1 not measured
• v1.34.0-dev FAIL
• v1.31.0 PASS 1 passing observations
• v1.29.1 not measured
• v1.28.0 not measured

Where it reproduced

• os=linux · runtime=go@1.26 ×1 2026-10-13 → 2026-10-13

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.31.0 → first failing release v1.34.0-dev

  What differs across the boundary

  • github.com/golang/protobuf v1.3.3, v1.4.2, v1.5.0, v1.5.2 → v1.5.4 hypothesis
  • github.com/google/go-cmp v0.4.0, v0.5.1, v0.5.5, v0.7.0 → v0.7.0 hypothesis
  • github.com/google/uuid — → v1.1.2 hypothesis
  • golang.org/x/net v0.0.0-20190311183353-d8887717615a, v0.0.0-20200707034311-ab3426394381, v0.0.0-20200822124328-c89045814202, v0.0.0-20210525063256-abc453219eb5, v0.4.0 → v0.55.0 hypothesis
  • golang.org/x/oauth2 v0.0.0-20180821212333-d2e6202438be, v0.0.0-20200107190931-bf48bf16ab8d, v0.0.0-20210514164344-f6687ab2804c, v0.0.0-20220223155221-ee480838109b → v0.0.0-20180821212333-d2e6202438be hypothesis
  • golang.org/x/sys v0.0.0-20190215142949-d0b11bdaac8a, v0.0.0-20200803210538-64077c9b5642, v0.0.0-20220114195835-da31bd327af9, v0.47.0 → v0.45.0 hypothesis
  • google.golang.org/genproto v0.0.0-20190819201941-24fa4b261c55, v0.0.0-20200804131852-c06518451d9c, v0.0.0-20200825200019-8632dd797987 → v0.0.0-20190819201941-24fa4b261c55 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 v1.34.0-dev → first passing release v1.71.0

  Releases between them never measured at this stage: 4

  What differs across the boundary

  • github.com/cespare/xxhash/v2 v2.3.0 → — hypothesis
  • github.com/cncf/udpa/go — → v0.0.0-20191209042840-269d4d468f6f hypothesis
  • github.com/cncf/xds/go v0.0.0-20241223141626-cff3c89139a3 → — hypothesis
  • github.com/envoyproxy/go-control-plane v0.13.4 → v0.9.4 hypothesis
  • github.com/envoyproxy/go-control-plane/envoy v1.32.4 → — hypothesis
  • github.com/golang/glog v1.2.4 → v0.0.0-20160126235308-23def4e6c14b hypothesis
  • github.com/google/go-cmp v0.6.0, v0.7.0 → v0.7.0 hypothesis
  • github.com/google/uuid v1.6.0 → v1.1.2 hypothesis
  • go.opentelemetry.io/contrib/detectors/gcp v1.34.0 → — hypothesis
  • go.opentelemetry.io/otel v1.34.0, v1.35.0 → — hypothesis
  • go.opentelemetry.io/otel/metric v1.34.0, v1.35.0 → — hypothesis
  • go.opentelemetry.io/otel/sdk v1.34.0, v1.35.0 → — hypothesis
  • go.opentelemetry.io/otel/sdk/metric v1.34.0 → — hypothesis
  • go.opentelemetry.io/otel/trace v1.34.0, v1.35.0 → — hypothesis
  • golang.org/x/net v0.34.0, v0.35.0, v0.38.0 → v0.55.0 hypothesis
  • golang.org/x/oauth2 v0.25.0, v0.26.0 → v0.0.0-20180821212333-d2e6202438be hypothesis
  • golang.org/x/sync v0.10.0, v0.11.0, v0.12.0 → — hypothesis
  • golang.org/x/sys v0.29.0, v0.30.0, v0.31.0 → v0.45.0 hypothesis
  • google.golang.org/genproto — → v0.0.0-20190819201941-24fa4b261c55 hypothesis
  • google.golang.org/genproto/googleapis/rpc v0.0.0-20250115164207-1a7da9e5054f, v0.0.0-20250218202821-56aae31c358a, v0.0.0-20250313205543-e70fdf4c4cb4 → — hypothesis
  • google.golang.org/protobuf v1.36.11, v1.36.5 → — 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: 5
• No failure domain was inferred for this failure.

Published answers for the affected releases

No published sample names these releases.