Recordsgolanggolang.org/x/lintfailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×1
Attrs with GenerationMatch/MetagenerationMatch failed: googleapi: Error 401: Anonymous caller does not have storage.objects.get access to the Google Cloud …
Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-10-18 · Last seen: 2026-10-18
sha256:253d5d5b625b…
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-20210508222113-6edffad5e616 not measured
- v0.0.0-20200302205851-738671d3881b not measured
- v0.0.0-20200130185559-910be7a94367 not measured
- v0.0.0-20191125180803-fdd1cda4f05f FAIL
- v0.0.0-20190930215403-16217165b5de not measured
- v0.0.0-20190909230951-414d861bb4ac not measured
- v0.0.0-20190409202823-959b441ac422 not measured
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-10-18 → 2026-10-18
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-20210508222113-6edffad5e616 | v0.0.0-20200302205851-738671d3881b | v0.0.0-20200130185559-910be7a94367 | v0.0.0-20191125180803-fdd1cda4f05f | v0.0.0-20190930215403-16217165b5de | v0.0.0-20190909230951-414d861bb4ac | v0.0.0-20190409202823-959b441ac422 |
|---|---|---|---|---|---|---|---|
| golang.org/x/tools | v0.0.0-20200130002326-2f3ba24bd6e7 | v0.1.12 | v0.0.0-20200204074204-1cc6d1ef6c74 | v0.0.0-20200122220014-bf1340f18c4a | v0.0.0-20191029041327-9cc4af7d6b2c | v0.0.0-20190911174233-4f2ddba30aff | v0.0.0-20190506145303-2d16b83fe98c |
Moved: 1 · 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.