Recordsgolanggolang.org/x/netfailure issue
Failure signature
UNKNOWN exit 2 EVERYTHING Evidence gap ×3
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-02
sha256:d29a2deca319…
golang.org/x/net/idna.Lookup golang.org/x/net/idna.ToASCII golang.org/x/net/idna.ToUnicode golang.org/x/net/publicsuffix.EffectiveTLDPlusOne golang.org/x/net/publicsuffix.List golang.org/x/net/publicsuffix.PublicSuffix
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.55.0 not measured
- v0.53.0 not measured
- v0.52.0 FAIL
- v0.51.0 not measured
- v0.50.0 not measured
- v0.4.0 not measured
- v0.2.0 not measured
- v0.0.0-20220403103023-749bd193bc2b FAIL
- v0.0.0-20210726213435-c6fcb2dbf985 not measured
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×3 2026-08-30 → 2026-09-02
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.55.0 | v0.53.0 | v0.52.0 | v0.51.0 | v0.50.0 | v0.4.0 | v0.2.0 | v0.0.0-20220403103023-749bd193bc2b |
|---|---|---|---|---|---|---|---|---|
| golang.org/x/crypto | v0.52.0 | v0.50.0 | v0.49.0 | v0.48.0 | v0.48.0 | — | — | — |
| golang.org/x/sys | v0.45.0 | v0.47.0 | v0.42.0 | v0.41.0 | v0.41.0 | v0.47.0 | v0.2.0 | — |
| golang.org/x/term | v0.43.0 | v0.42.0 | v0.41.0 | v0.40.0 | v0.40.0 | — | v0.2.0 | — |
| golang.org/x/text | v0.37.0 | v0.36.0 | v0.35.0 | v0.34.0 | v0.34.0 | v0.5.0 | v0.4.0 | — |
Moved: 4 · 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: 7
- No failure domain was inferred for this failure.
Published answers for the affected releases
- golang.org/x/net v0.0.0-20220403103023-749bd193bc2b: proxy.Direct, proxy.FromEnvironment, proxy.SOCKS5 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. HOWgolang.org/x/net/proxy.Directgolang.org/x/net/proxy.FromEnvironmentgolang.org/x/net/proxy.SOCKS5 MIT-0 · 2026-08-27