Recordsgolanggoogle.golang.org/genproto/googleapis/apifailure issue
Failure signature
PROJECT_COMPILE exit 1 ×1
<path> undefined: sdkmetric.WithAttributes
Evidence quality: complete · go/compiler · compiler-diagnostic · outer go test · First recorded: 2026-08-31 · Last seen: 2026-08-31
sha256:089d53aa715f…
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-20251029180050-ab9386a59fda PASS 1 passing observations
- v0.0.0-20250728155136-f173205681a0 not measured
- v0.0.0-20250303144028-a0af3efb3deb not measured
- v0.0.0-20250218202821-56aae31c358a not measured
- v0.0.0-20250115164207-1a7da9e5054f FAIL
- v0.0.0-20241007155032-5fefd90f89a9 not measured
- v0.0.0-20240826202546-f6391c0de4c7 not measured
- v0.0.0-20240401170217-c3f982113cda 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 failing release v0.0.0-20250115164207-1a7da9e5054f → first passing release v0.0.0-20251029180050-ab9386a59fda
Releases between them never measured at this stage: 3
One side of this boundary has no resolved dependency tree, so nothing could be compared.
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-20251029180050-ab9386a59fda | v0.0.0-20250728155136-f173205681a0 | v0.0.0-20250218202821-56aae31c358a | v0.0.0-20241007155032-5fefd90f89a9 | v0.0.0-20240826202546-f6391c0de4c7 | v0.0.0-20240401170217-c3f982113cda |
|---|---|---|---|---|---|---|
| google.golang.org/genproto/googleapis/rpc | v0.0.0-20251014184007-4626949a642f | v0.0.0-20250721164621-a45f3dfb1074 | v0.0.0-20250218202821-56aae31c358a | v0.0.0-20241007155032-5fefd90f89a9 | v0.0.0-20240826202546-f6391c0de4c7 | — |
| google.golang.org/grpc | v1.71.0 | v1.71.0 | v1.71.0 | v1.67.1 | v1.65.0 | v1.63.2 |
| google.golang.org/protobuf | v1.36.12 | v1.36.6 | v1.36.5 | v1.35.1 | v1.34.2 | v1.33.0 |
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
- Releases in this window never measured at PROJECT_COMPILE: 6
- No resolved dependency tree for v0.0.0-20251029180050-ab9386a59fda or for v0.0.0-20250115164207-1a7da9e5054f, 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.