Recordsgolanggolang.org/x/toolsfailure issue
Failure signature
UNKNOWN exit 2 EVERYTHING Evidence gap ×2
csx sample: unknown subcommand <str> · usage: csx sample <subcommand> · propose --goal G [--package purl]... [--symbol s]... …
Evidence quality: complete · unclassified-diagnostic · gap stage-unknown · First recorded: 2026-08-30 · Last seen: 2026-09-19
sha256:d29a2deca319…
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.10.0 not measured
- v0.6.0 not measured
- v0.1.12 not measured
- v0.1.10 FAIL
- v0.1.6-0.20210726203631-07bc1bf47fb2 not measured
- v0.1.5 not measured
- v0.0.0-20190312170243-e65039ee4138 not measured
- v0.0.0-20190311212946-11955173bddd not measured
- v0.0.0-20190226205152-f727befe758c FAIL
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×1 2026-08-30 → 2026-08-30
- os=linux · runtime=go@1.26 ×1 2026-09-19 → 2026-09-19
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.6.0 | v0.1.12 | v0.1.10 | v0.1.5 | v0.0.0-20190312170243-e65039ee4138 | v0.0.0-20190311212946-11955173bddd | v0.0.0-20190226205152-f727befe758c |
|---|---|---|---|---|---|---|---|
| github.com/yuin/goldmark | v1.4.13 | v1.4.13 | — | v1.3.5 | — | — | — |
| golang.org/x/mod | v0.8.0 | v0.6.0-dev.0.20220419223038-86c51ed26bb4 | — | v0.4.2 | — | — | — |
| golang.org/x/net | v0.10.0 | v0.4.0 | — | v0.0.0-20210405180319-a5a99cb37ef4 | v0.0.0-20190603091049-60506f45cf65 | v0.0.0-20190311183353-d8887717615a | v0.0.0-20190313220215-9f648a60d977 |
| golang.org/x/sync | v0.1.0 | v0.21.0 | — | v0.0.0-20210220032951-036812b2e83c | — | — | — |
| golang.org/x/sys | v0.17.0 | v0.47.0 | — | v0.8.0 | — | — | — |
| golang.org/x/text | — | v0.5.0 | — | — | — | — | — |
| golang.org/x/xerrors | — | — | — | v0.0.0-20200804184101-5ec99f83aff1 | — | — | — |
| google.golang.org/appengine | — | — | — | — | — | — | v1.4.0 |
Moved: 5 · unchanged at every release: 3
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: 7
- No failure domain was inferred for this failure.
Published answers for the affected releases
- golang.org/x/tools v0.1.10 This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOW MIT-0 · 2026-08-27