Recordsgolanggoogle.golang.org/genproto/googleapis/apifailure issue
Failure signature
PROJECT_TEST exit 1 ×1
FAIL example.com/otlptracegrpc-sample [setup failed] · FAIL example.com/otlptracegrpc-sample/test [setup failed]
Evidence quality: complete · go/test · test-runner-diagnostic · outer go test · First recorded: 2026-08-31 · Last seen: 2026-08-31
sha256:709c25d9be08…
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-20260720211330-0afa2a65878a PASS 1 passing observations
- v0.0.0-20260526163538-3dc84a4a5aaa PASS 1 passing observations
- v0.0.0-20260406210006-6f92a3bedf2d PASS 23 passing observations
- v0.0.0-20260401024825-9d38bb4040a9 FAIL
- v0.0.0-20260209200024-4cfbd4190f57 PASS 4 passing observations
- v0.0.0-20250728155136-f173205681a0 PASS 3 passing observations
- v0.0.0-20250303144028-a0af3efb3deb PASS 2 passing observations
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-20260209200024-4cfbd4190f57 → first failing release v0.0.0-20260401024825-9d38bb4040a9
One side of this boundary has no resolved dependency tree, so nothing could be compared.
-
Last failing release v0.0.0-20260401024825-9d38bb4040a9 → first passing release v0.0.0-20260406210006-6f92a3bedf2d
What differs across the boundary
- google.golang.org/genproto/googleapis/rpc v0.0.0-20260406210006-6f92a3bedf2d, v0.0.0-20260427160629-7cedc36a6bc4 → v0.0.0-20260401024825-9d38bb4040a9 hypothesis
- google.golang.org/grpc v1.80.0, v1.81.0 → v1.80.0 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.
| Library | v0.0.0-20260406210006-6f92a3bedf2d | v0.0.0-20260401024825-9d38bb4040a9 | v0.0.0-20250728155136-f173205681a0 |
|---|---|---|---|
| google.golang.org/genproto/googleapis/rpc | v0.0.0-20260427160629-7cedc36a6bc4 | v0.0.0-20260401024825-9d38bb4040a9 | v0.0.0-20250721164621-a45f3dfb1074 |
| google.golang.org/grpc | v1.81.0 | v1.80.0 | v1.71.0 |
| google.golang.org/protobuf | v1.36.11 | v1.36.11 | v1.36.6 |
Moved: 3 · 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
- No resolved dependency tree for v0.0.0-20260209200024-4cfbd4190f57 or for v0.0.0-20260401024825-9d38bb4040a9, so the versions either side of the boundary could not be compared.
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.