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.83.2 PASS 3 passing observations
• v1.83.1 PASS 11 passing observations
• v1.83.0 FAIL
• v1.83.0-dev not measured
• v1.81.0 PASS 6 passing observations
• v1.80.0 PASS 76 passing observations

Where it reproduced

• os=windows · runtime=go@1.26 ×1 2026-09-01 → 2026-09-01

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.81.0 → first failing release v1.83.0

  Releases between them never measured at this stage: 1

  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-20260202195803-dba9d589def2 hypothesis
  • github.com/envoyproxy/go-control-plane — → v0.14.0 hypothesis
  • github.com/envoyproxy/go-control-plane/envoy — → v1.37.0 hypothesis
  • github.com/golang/glog — → v1.2.5 hypothesis
  • github.com/spiffe/go-spiffe/v2 — → v2.7.0 hypothesis
  • go.opentelemetry.io/contrib/detectors/gcp — → v1.44.0 hypothesis
  • go.opentelemetry.io/otel v1.43.0 → v1.44.0 hypothesis
  • go.opentelemetry.io/otel/metric v1.43.0 → v1.44.0 hypothesis
  • go.opentelemetry.io/otel/sdk v1.43.0 → v1.44.0 hypothesis
  • go.opentelemetry.io/otel/sdk/metric v1.43.0 → v1.44.0 hypothesis
  • go.opentelemetry.io/otel/trace v1.43.0 → v1.44.0 hypothesis
  • gonum.org/v1/gonum — → v0.17.0 hypothesis
  • google.golang.org/genproto/googleapis/rpc v0.0.0-20260427160629-7cedc36a6bc4 → v0.0.0-20260526163538-3dc84a4a5aaa 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.83.0 → first passing release v1.83.1

  What differs across the boundary

  • go.opentelemetry.io/otel v1.46.0 → v1.44.0 hypothesis
  • go.opentelemetry.io/otel/metric v1.46.0 → v1.44.0 hypothesis
  • go.opentelemetry.io/otel/sdk v1.46.0 → v1.44.0 hypothesis
  • go.opentelemetry.io/otel/sdk/metric v1.46.0 → v1.44.0 hypothesis
  • go.opentelemetry.io/otel/trace v1.46.0 → v1.44.0 hypothesis
  • golang.org/x/net v0.58.0 → v0.55.0 hypothesis
  • golang.org/x/sync v0.22.0 → v0.20.0 hypothesis
  • golang.org/x/sys v0.47.0 → v0.45.0 hypothesis
  • google.golang.org/genproto/googleapis/rpc v0.0.0-20260819154853-08b0e4226688 → v0.0.0-20260526163538-3dc84a4a5aaa hypothesis
  • google.golang.org/protobuf v1.36.12 → v1.36.11 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_TEST: 1
• No failure domain was inferred for this failure.

Published answers for the affected releases

• google.golang.org/grpc v1.83.0: Invoke performs unary RPC dispatch over a ClientConn, executing unary interceptor chains and populating CallOption response metadata 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.Invokego MIT-0 · 2026-08-17
• google.golang.org/grpc v1.83.0: Configure gRPC-Go client and server receive message size limits to handle payloads exceeding the default 4MB limit 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.NewServergoogle.golang.org/grpc.NewClientgoogle.golang.org/grpc.MaxRecvMsgSizegoogle.golang.org/grpc.MaxCallRecvMsgSizegoogle.golang.org/grpc.MaxCallSendMsgSizegoogle.golang.org/grpc.WithDefaultCallOptionsgoogle.golang.org/grpc.WithContextDialergoogle.golang.org/grpc.WithTransportCredentialsgoogle.golang.org/grpc.ClientConn.Invokegoogle.golang.org/grpc/status.Codegoogle.golang.org/grpc/codes.ResourceExhaustedgo 1.26 MIT-0 · 2026-08-17
• google.golang.org/grpc v1.83.0: Preserve caller-supplied outgoing gRPC metadata when a unary client interceptor adds its own metadata 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.NewServergoogle.golang.org/grpc.Server.RegisterServicegoogle.golang.org/grpc.NewClientgoogle.golang.org/grpc.WithContextDialergoogle.golang.org/grpc.WithTransportCredentialsgoogle.golang.org/grpc.WithUnaryInterceptorgoogle.golang.org/grpc.ClientConn.Invokegoogle.golang.org/grpc/test/bufconn.Listengoogle.golang.org/grpc/metadata.NewOutgoingContextgoogle.golang.org/grpc/metadata.AppendToOutgoingContextgoogle.golang.org/grpc/metadata.FromIncomingContextgoogle.golang.org/grpc/status.Codego 1.26 MIT-0 · 2026-08-17