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

Where it was measured

PASS means the release recorded a passing observation at PROJECT_TEST and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.

• v1.78.0 PASS 8 passing observations
• v1.75.1 PASS 2 passing observations
• v1.72.1 PASS 2 passing observations
• v1.71.0 FAIL
• v1.69.4 PASS 2 passing observations
• v1.67.1 PASS 5 passing observations
• v1.63.2 not measured

Where it reproduced

• os=linux · runtime=go@1.26 ×1 2026-09-02 → 2026-09-02

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.69.4 → first failing release v1.71.0

  One side of this boundary has no resolved dependency tree, so nothing could be compared.

• Last failing release v1.71.0 → first passing release v1.72.1

  What differs across the boundary

  • github.com/cncf/xds/go v0.0.0-20250121191232-2f005788dc42 → v0.0.0-20241223141626-cff3c89139a3 hypothesis
  • github.com/spiffe/go-spiffe/v2 v2.5.0 → — hypothesis
  • go.opentelemetry.io/otel v1.34.0, v1.36.0 → v1.34.0, v1.35.0 hypothesis
  • go.opentelemetry.io/otel/metric v1.34.0, v1.36.0 → v1.34.0, v1.35.0 hypothesis
  • go.opentelemetry.io/otel/sdk v1.34.0, v1.36.0 → v1.34.0, v1.35.0 hypothesis
  • go.opentelemetry.io/otel/trace v1.34.0, v1.36.0 → v1.34.0, v1.35.0 hypothesis
  • golang.org/x/net v0.35.0, v0.40.0 → v0.34.0, v0.35.0, v0.38.0 hypothesis
  • golang.org/x/oauth2 v0.26.0 → v0.25.0, v0.26.0 hypothesis
  • golang.org/x/sync v0.11.0, v0.14.0 → v0.10.0, v0.11.0, v0.12.0 hypothesis
  • golang.org/x/sys v0.30.0, v0.33.0 → v0.29.0, v0.30.0, v0.31.0 hypothesis
  • google.golang.org/genproto/googleapis/rpc v0.0.0-20250218202821-56aae31c358a, v0.0.0-20250519155744-55703ea1f237 → v0.0.0-20250115164207-1a7da9e5054f, v0.0.0-20250218202821-56aae31c358a, v0.0.0-20250313205543-e70fdf4c4cb4 hypothesis
  • google.golang.org/protobuf v1.36.5, v1.36.6 → 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: 19 · unchanged at every release: 3

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_TEST: 1
• No resolved dependency tree for v1.69.4 or for v1.71.0, 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

• google.golang.org/grpc v1.71.0: ChainUnaryInterceptor Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgoogle.golang.org/grpc.ChainUnaryInterceptor MIT-0 · 2026-09-02
• google.golang.org/grpc v1.71.0: Chain multiple unary server interceptors with ChainUnaryInterceptor in grpc Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgoogle.golang.org/grpc.ChainUnaryInterceptor MIT-0 · 2026-09-02