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

• v0.0.0-20241007155032-5fefd90f89a9 PASS 18 passing observations
• v0.0.0-20240826202546-f6391c0de4c7 PASS 3 passing observations
• v0.0.0-20240814211410-ddb44dafa142 PASS 2 passing observations
• v0.0.0-20230711160842-782d3b101e98 FAIL

Where it reproduced

• os=linux · runtime=go@1.26 ×1 2026-08-26 → 2026-08-26

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 failing release v0.0.0-20230711160842-782d3b101e98 → first passing release v0.0.0-20240814211410-ddb44dafa142

  What differs across the boundary

  • google.golang.org/genproto — → v0.0.0-20230711160842-782d3b101e98 hypothesis
  • google.golang.org/protobuf v1.34.2, v1.35.2 → v1.31.0 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: 1 · unchanged at every release: 1

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

• The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
• No failure domain was inferred for this failure.

Published answers for the affected releases

No published sample names these releases.