Recordsgolanggithub.com/pelletier/go-toml/v2failure issue
Failure signature
PROJECT_TEST exit 1 ERROR ×2
--- FAIL: TestTheRemoteRunnerIsFailClosed (0.71s) …
Evidence quality: complete · go/test · test-runner-diagnostic · outer go test · First recorded: 2026-09-15 · Last seen: 2026-09-15
sha256:1e6b1e2fdeb5…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TEST 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-15 → 2026-09-15
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 v2.2.4 → first failing release v2.4.3
One side of this boundary has no resolved dependency tree, so nothing could be compared.
Evidence gaps
- No resolved dependency tree for v2.2.4 or for v2.4.3, so the versions either side of the boundary could not be compared.
- 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