Recordsgolanggithub.com/grpc-ecosystem/grpc-gateway/v2failure 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.
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 v2.25.1 → first passing release v2.28.0
Releases between them never measured at this stage: 2
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.
Moved: 6 · unchanged at every release: 5
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: 2
- No resolved dependency tree for v2.28.0 or for v2.25.1, 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.