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-20260706201446-f0a921348800 PASS 6 passing observations
• v0.0.0-20260630182238-925bb5da69e7 PASS 2 passing observations
• v0.0.0-20260526163538-3dc84a4a5aaa PASS 6 passing observations
• v0.0.0-20260427160629-7cedc36a6bc4 FAIL
• v0.0.0-20260406210006-6f92a3bedf2d PASS 17 passing observations
• v0.0.0-20260401024825-9d38bb4040a9 PASS 57 passing observations
• v0.0.0-20260401001100-f93e5f3e9f0f not measured

Where it reproduced

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

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-20260427160629-7cedc36a6bc4

  What differs across the boundary

  • google.golang.org/protobuf v1.36.11 → 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-20260427160629-7cedc36a6bc4 → first passing release v0.0.0-20260526163538-3dc84a4a5aaa

  What differs across the boundary

  • google.golang.org/protobuf v1.36.11 → 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: 1
• No failure domain was inferred for this failure.

Published answers for the affected releases

• google.golang.org/genproto/googleapis/rpc v0.0.0-20260427160629-7cedc36a6bc4: attribute_context.AttributeContext 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.AttributeContextgo MIT-0 · 2026-09-01
• google.golang.org/genproto/googleapis/rpc v0.0.0-20260427160629-7cedc36a6bc4: errdetails.RequestInfo 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.RequestInfo MIT-0 · 2026-08-28