Recordsgolanggolang.org/x/netfailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×14
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-08-30 · Last seen: 2026-10-24
sha256:3b3190f2cd44…
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.53.0 not measured
- v0.52.0 FAIL
- v0.51.0 not measured
- v0.46.0 FAIL
- v0.38.0 FAIL
- v0.17.0 FAIL
- v0.12.0 FAIL
- v0.0.0-20210503060351-7fd8e65b6420 FAIL
- v0.0.0-20210119194325-5f4716e94777 FAIL
Where it reproduced
- os=linux · runtime=go@1.26 ×14 2026-08-30 → 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.53.0 | v0.52.0 | v0.51.0 | v0.46.0 | v0.38.0 | v0.17.0 | v0.12.0 | v0.0.0-20210503060351-7fd8e65b6420 | v0.0.0-20210119194325-5f4716e94777 |
|---|---|---|---|---|---|---|---|---|---|
| golang.org/x/crypto | v0.50.0 | v0.49.0 | v0.48.0 | v0.43.0 | v0.36.0 | v0.14.0 | v0.11.0 | — | — |
| golang.org/x/sys | v0.47.0 | v0.42.0 | v0.41.0 | v0.37.0 | v0.31.0 | v0.14.0 | v0.10.0 | v0.0.0-20210806184541-e5e7981a1069 | v0.0.0-20210124154548-22da62e12c0c |
| golang.org/x/term | v0.42.0 | v0.41.0 | v0.40.0 | v0.36.0 | v0.30.0 | v0.13.0 | v0.10.0 | v0.0.0-20201126162022-7de9c90e9dd1 | v0.0.0-20201126162022-7de9c90e9dd1 |
| golang.org/x/text | v0.36.0 | v0.35.0 | v0.34.0 | v0.30.0 | v0.23.0 | v0.13.0 | v0.11.0 | v0.3.6 | v0.3.5 |
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: 2
- No failure domain was inferred for this failure.
Published answers for the affected releases
- golang.org/x/net v0.38.0: idna.Lookup 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/idna.Lookup MIT-0 · 2026-08-30
- golang.org/x/net v0.38.0: idna.ToUnicode 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/idna.ToUnicode MIT-0 · 2026-08-26
- golang.org/x/net v0.38.0: idna.ToASCII 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/idna.ToASCII MIT-0 · 2026-08-26