Recordsgolanggithub.com/mattn/go-sqlite3failure issue
Failure signature
PROJECT_PROCESS Evidence gap ×1
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-19 · Last seen: 2026-08-19
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.
Where it reproduced
- os=windows · runtime=go@1.26 ×1 2026-08-19 → 2026-08-19
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 failing release v1.14.24 → first passing release v1.14.49
Both trees resolved every dependency to the same version. Nothing here moved.
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
- github.com/mattn/go-sqlite3 v1.14.24: go-sqlite3 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. HOWgithub.com/mattn/go-sqlite3go 1.26.6 MIT-0 · 2026-08-27