Recordsgolanggithub.com/pelletier/go-toml/v2failure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×2
Traceback (most recent call last): · File <str>, line 120, in <module> · main() · File <str>, line 42, in main
Evidence quality: complete · python · unclassified-diagnostic · outer python · gap stage-unknown · First recorded: 2026-09-13 · Last seen: 2026-09-13
sha256:30c7aeb70296…
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.
Where it reproduced
- os=windows · runtime=go@1.26 ×2 2026-09-13 → 2026-09-13
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.
- Releases in this window never measured at UNKNOWN: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/pelletier/go-toml/v2 v2.4.3 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-09-13