Recordsgolanggolang.org/x/netfailure issue
Failure signature
PROJECT_PROCESS ERR_ASSERTION Evidence gap ×8
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-26 · Last seen: 2026-08-27
Where it was measured
PASS means the release recorded a passing observation at PROJECT_PROCESS and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- v0.38.0 PASS 14 passing observations
- v0.37.0 FAIL
- v0.35.0 PASS 6 passing observations
- v0.34.0 PASS 1 passing observations
- v0.29.0 FAIL
- v0.28.0 PASS 10 passing observations
- v0.2.0 PASS 23 passing observations
- v0.0.0-20220403103023-749bd193bc2b FAIL
- v0.0.0-20210525063256-abc453219eb5 PASS 45 passing observations
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×6 2026-08-26 → 2026-08-27
- os=linux · runtime=go@1.26 ×2 2026-08-26 → 2026-08-26
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last passing release v0.0.0-20210525063256-abc453219eb5 → first failing release v0.0.0-20220403103023-749bd193bc2b
Releases between them never measured at this stage: 1
What differs across the boundary
- golang.org/x/sys v0.0.0-20210423082822-04245dca01da, v0.0.0-20220114195835-da31bd327af9, v0.47.0 → — hypothesis
- golang.org/x/term v0.0.0-20201126162022-7de9c90e9dd1 → — hypothesis
- golang.org/x/text v0.3.6 → — hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
-
Last failing release v0.0.0-20220403103023-749bd193bc2b → first passing release v0.2.0
What differs across the boundary
- golang.org/x/sys v0.2.0 → — hypothesis
- golang.org/x/term v0.2.0 → — hypothesis
- golang.org/x/text v0.4.0 → — hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
-
Last passing release v0.28.0 → first failing release v0.29.0
What differs across the boundary
- golang.org/x/crypto v0.26.0 → v0.27.0 hypothesis
- golang.org/x/sys v0.23.0, v0.24.0 → v0.25.0 hypothesis
- golang.org/x/term v0.23.0 → v0.24.0 hypothesis
- golang.org/x/text v0.17.0 → v0.18.0 hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
-
Last failing release v0.29.0 → first passing release v0.34.0
Releases between them never measured at this stage: 1
What differs across the boundary
- golang.org/x/crypto v0.32.0 → v0.27.0 hypothesis
- golang.org/x/sys v0.29.0 → v0.25.0 hypothesis
- golang.org/x/term v0.28.0 → v0.24.0 hypothesis
- golang.org/x/text v0.21.0 → v0.18.0 hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
-
Last passing release v0.35.0 → first failing release v0.37.0
What differs across the boundary
- golang.org/x/crypto v0.33.0 → v0.36.0 hypothesis
- golang.org/x/sys v0.30.0 → v0.31.0 hypothesis
- golang.org/x/term v0.29.0 → v0.30.0 hypothesis
- golang.org/x/text v0.22.0 → v0.23.0 hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
-
Last failing release v0.37.0 → first passing release v0.38.0
Both trees resolved every dependency to the same version. Nothing here moved.
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.38.0 | v0.37.0 | v0.35.0 | v0.34.0 | v0.29.0 | v0.28.0 | v0.2.0 | v0.0.0-20220403103023-749bd193bc2b | v0.0.0-20210525063256-abc453219eb5 |
|---|---|---|---|---|---|---|---|---|---|
| golang.org/x/crypto | v0.36.0 | v0.36.0 | v0.33.0 | v0.32.0 | v0.27.0 | v0.26.0 | — | — | — |
| golang.org/x/sys | v0.31.0 | v0.31.0 | v0.30.0 | v0.29.0 | v0.25.0 | v0.24.0 | v0.2.0 | — | v0.47.0 |
| golang.org/x/term | v0.30.0 | v0.30.0 | v0.29.0 | v0.28.0 | v0.24.0 | v0.23.0 | v0.2.0 | — | v0.0.0-20201126162022-7de9c90e9dd1 |
| golang.org/x/text | v0.23.0 | v0.23.0 | v0.22.0 | v0.21.0 | v0.18.0 | v0.17.0 | v0.4.0 | — | v0.3.6 |
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.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- golang.org/x/net v0.37.0: websocket 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/websocket MIT-0 · 2026-09-02
- golang.org/x/net v0.37.0 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
- golang.org/x/net v0.29.0: websocket.Conn 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/websocket.Conn MIT-0 · 2026-09-04
- golang.org/x/net v0.29.0: atom.Form 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/html/atom.Form MIT-0 · 2026-09-04
- golang.org/x/net v0.29.0: atom.Button 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/html/atom.Button MIT-0 · 2026-09-04
- 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