Recordsgolanggithub.com/konsorten/go-windows-terminal-sequencesfailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×1
assertion 2 failed: text output still contains original keys: event_time=<str> log_level=warning payload=<str> · exit status 1
Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-09-19 · Last seen: 2026-09-19
sha256:9b04b8efd302…
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.
- v1.0.1 FAIL
Where it reproduced
- 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.
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.
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.