Recordsgolanggoogle.golang.org/genproto/googleapis/apifailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×1
doc: cannot find package <str> in any of: · ($GOROOT not set) · <path> (from $GOPATH)
Evidence quality: complete · go · unclassified-diagnostic · outer go · gap stage-unknown · First recorded: 2026-10-24 · Last seen: 2026-10-24
sha256:3b3190f2cd44…
Where it was measured
PASS means the release recorded a passing observation at UNKNOWN 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-20260316180232-0b37fe3546d5 not measured
- v0.0.0-20260209200024-4cfbd4190f57 not measured
- v0.0.0-20260128011058-8636f8732409 not measured
- v0.0.0-20251111163417-95abcf5c77ba FAIL
- v0.0.0-20251029180050-ab9386a59fda not measured
- v0.0.0-20250728155136-f173205681a0 not measured
- v0.0.0-20250303144028-a0af3efb3deb not measured
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-10-24 → 2026-10-24
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
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-20260316180232-0b37fe3546d5 | v0.0.0-20260128011058-8636f8732409 | v0.0.0-20251111163417-95abcf5c77ba | v0.0.0-20251029180050-ab9386a59fda | v0.0.0-20250728155136-f173205681a0 |
|---|---|---|---|---|---|
| google.golang.org/genproto/googleapis/rpc | v0.0.0-20260316180232-0b37fe3546d5 | v0.0.0-20260128011058-8636f8732409 | v0.0.0-20251111163417-95abcf5c77ba | v0.0.0-20251014184007-4626949a642f | v0.0.0-20250721164621-a45f3dfb1074 |
| google.golang.org/grpc | v1.79.2 | v1.78.0 | v1.76.0 | v1.71.0 | v1.71.0 |
| google.golang.org/protobuf | v1.36.11 | v1.36.12 | v1.36.10 | v1.36.12 | 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
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- The captured output could not establish: stage-unknown.
- No release in this window recorded a passing observation at UNKNOWN.
- Releases in this window never measured at UNKNOWN: 6
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.