Recordsgolanggolang.org/x/termfailure issue
Failure signature
PROCESS_START process start failed Evidence gap ×1
Evidence quality: partial · structured-termination · gap diagnostic-missing · First recorded: 2026-08-30 · Last seen: 2026-08-30
sha256:c12549970456…
Where it was measured
PASS means the release recorded a passing observation at PROCESS_START and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- v0.43.0 not measured
- v0.42.0 not measured
- v0.40.0 not measured
- v0.34.0 FAIL
- v0.30.0 not measured
- v0.22.0 not measured
- v0.17.0 not measured
Where it reproduced
- executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 ×1 2026-08-30 → 2026-08-30
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.43.0 | v0.42.0 | v0.40.0 | v0.30.0 | v0.22.0 | v0.17.0 |
|---|---|---|---|---|---|---|
| golang.org/x/sys | v0.45.0 | v0.43.0 | v0.41.0 | — | v0.22.0 | v0.17.0 |
Moved: 1 · 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: diagnostic-missing.
- No release in this window recorded a passing observation at PROCESS_START.
- Releases in this window never measured at PROCESS_START: 6
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.