Records/golang/google.golang.org/genproto/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.

• v0.0.0-20210821163610-241b8fcbd6c8 PASS 5 passing observations
• v0.0.0-20210813162853-db860fec028c not measured
• v0.0.0-20210805201207-89edb61ffb67 FAIL
• v0.0.0-20200825200019-8632dd797987 PASS 2 passing observations
• v0.0.0-20190819201941-24fa4b261c55 PASS 4 passing observations
• v0.0.0-20190801165951-fa694d86fc64 not measured
• v0.0.0-20190502173448-54afdca5d873 FAIL
• v0.0.0-20190307195333-5fe7a883aa19 not measured
• v0.0.0-20180817151627-c66870c02cf8 PASS 2 passing observations

Where it reproduced

• os=linux · runtime=go@1.26 ×2 2026-10-18 → 2026-10-22

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 v0.0.0-20180817151627-c66870c02cf8 → first failing release v0.0.0-20190502173448-54afdca5d873

  Releases between them never measured at this stage: 3

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

• Last failing release v0.0.0-20190502173448-54afdca5d873 → first passing release v0.0.0-20190819201941-24fa4b261c55

  Releases between them never measured at this stage: 1

  What differs across the boundary

  • github.com/golang/protobuf v1.3.2, v1.3.3, v1.5.4 → v1.3.1 hypothesis
  • golang.org/x/exp v0.0.0-20190121172915-509febef88a4, v0.0.0-20190510132918-efd6b22b2522 → v0.0.0-20190121172915-509febef88a4 hypothesis
  • golang.org/x/lint v0.0.0-20190313153728-d0100b6bd8b3, v0.0.0-20190409202823-959b441ac422 → v0.0.0-20190409202823-959b441ac422 hypothesis
  • golang.org/x/net — → v0.0.0-20190503192946-f4e77d36d62c hypothesis
  • golang.org/x/tools v0.0.0-20190524140312-2c0ae7006135, v0.0.0-20190628153133-6cdbf07be9d0, v0.44.0 → v0.0.0-20190506145303-2d16b83fe98c hypothesis
  • google.golang.org/grpc v1.21.1, v1.23.0, v1.25.1, v1.27.0, v1.31.0, v1.34.0-dev → v1.20.1 hypothesis
  • honnef.co/go/tools v0.0.0-20190418001031-e561f6794a2a, v0.0.0-20190523083050-ea95bdfd59fc → v0.0.0-20190418001031-e561f6794a2a 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 passing release v0.0.0-20200825200019-8632dd797987 → first failing release v0.0.0-20210805201207-89edb61ffb67

  What differs across the boundary

  • github.com/golang/protobuf v1.4.1, v1.4.2, v1.5.0, v1.5.2 → v1.5.2 hypothesis
  • golang.org/x/lint v0.0.0-20190313153728-d0100b6bd8b3, v0.0.0-20200302205851-738671d3881b → v0.0.0-20210508222113-6edffad5e616 hypothesis
  • golang.org/x/tools v0.0.0-20190524140312-2c0ae7006135, v0.0.0-20200825202427-b303f430e36d, v0.1.12 → v0.1.5 hypothesis
  • google.golang.org/grpc v1.27.0, v1.31.0 → v1.39.1 hypothesis
  • google.golang.org/protobuf v1.24.0, v1.25.0, v1.26.0, v1.36.11, v1.36.12 → v1.27.1 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 v0.0.0-20210805201207-89edb61ffb67 → first passing release v0.0.0-20210821163610-241b8fcbd6c8

  Releases between them never measured at this stage: 1

  What differs across the boundary

  • google.golang.org/grpc v1.40.0 → v1.39.1 hypothesis
  • google.golang.org/protobuf v1.27.1, v1.28.0 → v1.27.1 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: 8 · unchanged at every release: 0

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 resolved dependency tree for v0.0.0-20180817151627-c66870c02cf8 or for v0.0.0-20190502173448-54afdca5d873, 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

No published sample names these releases.