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.27.0 PASS 2 passing observations
• v1.26.0 PASS 1 passing observations
• v1.25.1 PASS 1 passing observations
• v1.23.0 FAIL
• v1.21.1 PASS 1 passing observations
• v1.20.1 PASS 1 passing observations
• v1.19.0 PASS 1 passing observations

Where it reproduced

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

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.21.1 → first failing release v1.23.0

  What differs across the boundary

  • github.com/golang/mock v1.3.1 → v1.1.1 hypothesis
  • github.com/golang/protobuf v1.3.2 → v1.3.2, v1.5.4 hypothesis
  • github.com/google/go-cmp v0.3.0 → v0.2.0, v0.5.5 hypothesis
  • golang.org/x/lint v0.0.0-20190409202823-959b441ac422, v0.0.0-20190909230951-414d861bb4ac, v0.0.0-20190930215403-16217165b5de → v0.0.0-20190313153728-d0100b6bd8b3 hypothesis
  • golang.org/x/net v0.0.0-20190620200207-3b0461eec859 → v0.0.0-20190311183353-d8887717615a hypothesis
  • golang.org/x/oauth2 v0.0.0-20190604053449-0f29369cfe45 → v0.0.0-20180821212333-d2e6202438be hypothesis
  • golang.org/x/sys v0.0.0-20190624142023-c5567b49c5d0 → v0.0.0-20190215142949-d0b11bdaac8a hypothesis
  • golang.org/x/tools v0.0.0-20190628153133-6cdbf07be9d0, v0.0.0-20190911174233-4f2ddba30aff, v0.0.0-20191113191852-77e3bb0ad9e7, v0.0.0-20191115202509-3a792d9c32b2 → v0.0.0-20190524140312-2c0ae7006135 hypothesis
  • google.golang.org/genproto v0.0.0-20190801165951-fa694d86fc64, v0.0.0-20190819201941-24fa4b261c55, v0.0.0-20190911173649-1774047e7e51, v0.0.0-20191108220845-16a3f7862a1a, v0.0.0-20191115194625-c23dd37a84c9 → v0.0.0-20190819201941-24fa4b261c55 hypothesis
  • honnef.co/go/tools v0.0.0-20190418001031-e561f6794a2a, v0.0.1-2019.2.3 → v0.0.0-20190523083050-ea95bdfd59fc 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.23.0 → first passing release v1.25.1

  What differs across the boundary

  • github.com/client9/misspell — → v0.3.4 hypothesis
  • github.com/envoyproxy/go-control-plane v0.9.0, v0.9.4 → — hypothesis
  • github.com/envoyproxy/protoc-gen-validate v0.1.0 → — hypothesis
  • github.com/golang/protobuf v1.3.2 → v1.3.2, v1.5.4 hypothesis
  • github.com/google/go-cmp v0.2.0 → v0.2.0, v0.5.5 hypothesis
  • golang.org/x/lint — → v0.0.0-20190313153728-d0100b6bd8b3 hypothesis
  • golang.org/x/tools — → v0.0.0-20190524140312-2c0ae7006135 hypothesis
  • honnef.co/go/tools — → v0.0.0-20190523083050-ea95bdfd59fc 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: 11 · 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

• No failure domain was inferred for this failure.

Published answers for the affected releases

No published sample names these releases.