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-20260401001100-f93e5f3e9f0f not measured
• v0.0.0-20260209200024-4cfbd4190f57 PASS 4 passing observations
• v0.0.0-20260128011058-8636f8732409 PASS 5 passing observations
• v0.0.0-20251029180050-ab9386a59fda FAIL
• v0.0.0-20250728155136-f173205681a0 PASS 7 passing observations
• v0.0.0-20250707201910-8d1bb00bc6a7 not measured
• v0.0.0-20250218202821-56aae31c358a PASS 6 passing observations

Where it reproduced

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

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-20250728155136-f173205681a0 → first failing release v0.0.0-20251029180050-ab9386a59fda

  What differs across the boundary

  • google.golang.org/protobuf v1.36.10, v1.36.12, v1.36.6 → v1.36.10, v1.36.11, v1.36.12 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-20251029180050-ab9386a59fda → first passing release v0.0.0-20260128011058-8636f8732409

  What differs across the boundary

  • google.golang.org/protobuf v1.36.11, v1.36.12 → v1.36.10, v1.36.11, v1.36.12 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: 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_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-20251029180050-ab9386a59fda: errdetails.DebugInfo 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.DebugInfogo MIT-0 · 2026-10-11
• google.golang.org/genproto/googleapis/rpc v0.0.0-20251029180050-ab9386a59fda: code.Code_RESOURCE_EXHAUSTED 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/code.Code_RESOURCE_EXHAUSTED MIT-0 · 2026-10-11
• google.golang.org/genproto/googleapis/rpc v0.0.0-20251029180050-ab9386a59fda: errdetails.BadRequest_FieldViolation 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.BadRequest_FieldViolation MIT-0 · 2026-10-11