Records/golang/google.golang.org/genproto/googleapis/api/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-20250303144028-a0af3efb3deb PASS 2 passing observations
• v0.0.0-20250218202821-56aae31c358a PASS 6 passing observations
• v0.0.0-20250115164207-1a7da9e5054f PASS 2 passing observations
• v0.0.0-20241007155032-5fefd90f89a9 FAIL
• v0.0.0-20240826202546-f6391c0de4c7 PASS 4 passing observations
• v0.0.0-20240401170217-c3f982113cda not measured

Where it reproduced

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

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-20240826202546-f6391c0de4c7 → first failing release v0.0.0-20241007155032-5fefd90f89a9

  What differs across the boundary

  • google.golang.org/genproto/googleapis/rpc v0.0.0-20240823204242-4ba0660f739c, v0.0.0-20240826202546-f6391c0de4c7 → v0.0.0-20241007155032-5fefd90f89a9 hypothesis
  • google.golang.org/grpc v1.65.0 → v1.67.1 hypothesis
  • google.golang.org/protobuf v1.34.2 → v1.35.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-20241007155032-5fefd90f89a9 → first passing release v0.0.0-20250115164207-1a7da9e5054f

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

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: 3 · 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

• The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
• Releases in this window never measured at PROJECT_TEST: 1
• No resolved dependency tree for v0.0.0-20250115164207-1a7da9e5054f or for v0.0.0-20241007155032-5fefd90f89a9, 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/genproto/googleapis/api v0.0.0-20241007155032-5fefd90f89a9: annotations.E_Http 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/genproto/googleapis/api/annotations.E_Http MIT-0 · 2026-08-30
• google.golang.org/genproto/googleapis/api v0.0.0-20241007155032-5fefd90f89a9: annotations.HttpRule_Put 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/genproto/googleapis/api/annotations.HttpRule_Put MIT-0 · 2026-08-27
• google.golang.org/genproto/googleapis/api v0.0.0-20241007155032-5fefd90f89a9: annotations.HttpRule_Post 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/genproto/googleapis/api/annotations.HttpRule_Post MIT-0 · 2026-08-27