Recordsgolanggoogle.golang.org/genproto/googleapis/rpcfailure issue
Failure signature
PROJECT_TEST exit 1 ×1
FAIL test_rpc [setup failed]
Evidence quality: complete · go/test · test-runner-diagnostic · outer go test · First recorded: 2026-09-04 · Last seen: 2026-09-04
sha256:85beceb65743…
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-20260904194346-d0f1323225a4 PASS 9 passing observations
- v0.0.0-20260831171406-18b4a7587f8a FAIL
- v0.0.0-20260825221802-da73d73af1c5 PASS 13 passing observations
- v0.0.0-20260819154853-08b0e4226688 PASS 11 passing observations
- v0.0.0-20260720211330-0afa2a65878a PASS 1 passing observations
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-09-04 → 2026-09-04
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-20260825221802-da73d73af1c5 → first failing release v0.0.0-20260831171406-18b4a7587f8a
Both trees resolved every dependency to the same version. Nothing here moved.
-
Last failing release v0.0.0-20260831171406-18b4a7587f8a → first passing release v0.0.0-20260904194346-d0f1323225a4
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.
| Library | v0.0.0-20260904194346-d0f1323225a4 | v0.0.0-20260831171406-18b4a7587f8a | v0.0.0-20260825221802-da73d73af1c5 | v0.0.0-20260819154853-08b0e4226688 |
|---|---|---|---|---|
| google.golang.org/protobuf | v1.36.12 | v1.36.12 | v1.36.12 | v1.36.12 |
Moved: 0 · 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
- No failure domain was inferred for this failure.
Published answers for the affected releases
- google.golang.org/genproto/googleapis/rpc v0.0.0-20260831171406-18b4a7587f8a: code.Code_UNAUTHENTICATED 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_UNAUTHENTICATED MIT-0 · 2026-09-04
- google.golang.org/genproto/googleapis/rpc v0.0.0-20260831171406-18b4a7587f8a: errdetails.BadRequest_FieldViolation 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-09-04
- google.golang.org/genproto/googleapis/rpc v0.0.0-20260831171406-18b4a7587f8a: errdetails.BadRequest 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.BadRequestgo MIT-0 · 2026-09-04