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-20250707201910-8d1bb00bc6a7 not measured
• v0.0.0-20250218202821-56aae31c358a PASS 6 passing observations
• v0.0.0-20250115164207-1a7da9e5054f PASS 4 passing observations
• v0.0.0-20241007155032-5fefd90f89a9 FAIL
• v0.0.0-20240826202546-f6391c0de4c7 PASS 3 passing observations
• v0.0.0-20240814211410-ddb44dafa142 not measured
• v0.0.0-20230711160842-782d3b101e98 PASS 2 passing observations

Where it reproduced

• 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/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

  What differs across the boundary

  • google.golang.org/protobuf v1.36.5 → 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.

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

• Releases in this window never measured at PROJECT_TEST: 2
• No failure domain was inferred for this failure.

Published answers for the affected releases

• google.golang.org/genproto/googleapis/rpc v0.0.0-20241007155032-5fefd90f89a9: code.Code_INTERNAL 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. HOWcode.Code_INTERNAL MIT-0 · 2026-08-27
• google.golang.org/genproto/googleapis/rpc v0.0.0-20241007155032-5fefd90f89a9: status.Status 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/rpc/status.Status MIT-0 · 2026-08-27
• google.golang.org/genproto/googleapis/rpc v0.0.0-20241007155032-5fefd90f89a9: errdetails.RetryInfo 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/rpc/errdetails.RetryInfo MIT-0 · 2026-08-27