Records/golang/google.golang.org/genproto/googleapis/rpc/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-20260904194346-d0f1323225a4 PASS 3 passing observations
• v0.0.0-20260831171406-18b4a7587f8a not measured
• v0.0.0-20260825221802-da73d73af1c5 FAIL
• v0.0.0-20260819154853-08b0e4226688 not measured
• v0.0.0-20260720211330-0afa2a65878a not measured
• v0.0.0-20260526163538-3dc84a4a5aaa not measured
• v0.0.0-20260406210006-6f92a3bedf2d PASS 1 passing observations

Where it reproduced

• os=linux · runtime=go@1.26 ×2 2026-09-08 → 2026-09-08

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-20260406210006-6f92a3bedf2d → first failing release v0.0.0-20260825221802-da73d73af1c5

  Releases between them never measured at this stage: 4

  What differs across the boundary

  • google.golang.org/protobuf 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-20260825221802-da73d73af1c5 → first passing release v0.0.0-20260904194346-d0f1323225a4

  Releases between them never measured at this stage: 1

  Both trees resolved every dependency to the same version. Nothing here moved.

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

• The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
• The captured output could not establish: diagnostic-missing.
• Releases in this window never measured at PROJECT_COMPILE: 4
• No failure domain was inferred for this failure.

Published answers for the affected releases

• google.golang.org/genproto/googleapis/rpc v0.0.0-20260825221802-da73d73af1c5: attribute_context.AttributeContext_Api 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/context/attribute_context.AttributeContext_Apigo 1.26.6 MIT-0 · 2026-09-07
• google.golang.org/genproto/googleapis/rpc v0.0.0-20260825221802-da73d73af1c5: code.Code_UNKNOWN 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_UNKNOWN MIT-0 · 2026-09-07
• google.golang.org/genproto/googleapis/rpc v0.0.0-20260825221802-da73d73af1c5: code.Code_UNIMPLEMENTED 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_UNIMPLEMENTED MIT-0 · 2026-09-07