Recordsgolanggithub.com/glebarez/sqlitefailure issue
Failure signature
PROJECT_TEST Evidence gap ×2
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-09-07 · Last seen: 2026-09-08
DB.AutoMigrate DB.Create DB.Delete DB.Find DB.First DB.Joins DB.Omit DB.Ping DB.Preload DB.Select DB.Unscoped DB.Update DB.Updates DB.Where Dialector Open clause.Associations gorm.Config.TranslateError gorm.DeletedAt gorm.ErrDuplicatedKey gorm.ErrRecordNotFound gorm.Open sql.Drivers sql.Open sqlite.Open
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.
- v1.11.0 FAIL
Where it reproduced
- executionContext=go · os=linux · runtime=go@1.26 ×2 2026-09-07 → 2026-09-08
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.
- No release in this window recorded a passing observation at PROJECT_TEST.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/glebarez/sqlite v1.11.0: Open 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/glebarez/sqlite.Opengo 1.26.6 MIT-0 · 2026-08-27