Recordsgolanggolang.org/x/toolsfailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×1
panic: proto: Marshal called with nil · goroutine 1 [running]: · cloud.google.com/go/datastore.(*Key).Encode(0x307cbcd84320?) · <path>:<n> +0x68
Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-10-18 · Last seen: 2026-10-18
sha256:7ec541984733…
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-20191029041327-9cc4af7d6b2c not measured
- v0.0.0-20190911174233-4f2ddba30aff not measured
- v0.0.0-20190823170909-c4a336ef6a2f not measured
- v0.0.0-20190628153133-6cdbf07be9d0 FAIL
- v0.0.0-20190621195816-6e04913cbbac not measured
- v0.0.0-20190524140312-2c0ae7006135 not measured
- v0.0.0-20190506145303-2d16b83fe98c 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-20191029041327-9cc4af7d6b2c | v0.0.0-20190911174233-4f2ddba30aff | v0.0.0-20190823170909-c4a336ef6a2f | v0.0.0-20190628153133-6cdbf07be9d0 | v0.0.0-20190621195816-6e04913cbbac | v0.0.0-20190524140312-2c0ae7006135 | v0.0.0-20190506145303-2d16b83fe98c |
|---|---|---|---|---|---|---|---|
| golang.org/x/net | v0.0.0-20190620200207-3b0461eec859 | v0.0.0-20190620200207-3b0461eec859 | v0.0.0-20190620200207-3b0461eec859 | v0.0.0-20190620200207-3b0461eec859 | v0.0.0-20190404232315-eb5bcb51f2a3 | v0.0.0-20190628185345-da137c7871d7 | v0.0.0-20190311183353-d8887717615a |
| golang.org/x/sync | v0.0.0-20190423024810-112230192c58 | v0.0.0-20190423024810-112230192c58 | v0.0.0-20190423024810-112230192c58 | v0.0.0-20190423024810-112230192c58 | v0.0.0-20190423024810-112230192c58 | v0.0.0-20190423024810-112230192c58 | v0.0.0-20190423024810-112230192c58 |
| golang.org/x/xerrors | v0.0.0-20190717185122-a985d3407aa7 | v0.0.0-20190717185122-a985d3407aa7 | v0.0.0-20190717185122-a985d3407aa7 | — | — | — | — |
Moved: 1 · unchanged at every release: 2
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.