Recordsgolanggorm.io/gormfailure issue
Failure signature
PROJECT_TEST Evidence gap ×2
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-09-07 · Last seen: 2026-09-08
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
- 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.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
| Library | v1.31.2 | v1.25.7 |
|---|---|---|
| github.com/jinzhu/inflection | v1.0.0 | v1.0.0 |
| github.com/jinzhu/now | v1.1.5 | v1.1.5 |
| golang.org/x/text | v0.20.0 | — |
Moved: 0 · unchanged at every release: 3
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.
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
- gorm.io/gorm v1.31.2: Prove clause.OnConflict upsert semantics in GORM v1.31.2 across DoNothing, UpdateAll, selective AssignmentColumns, and expression assignments 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. HOWgorm.OpenDB.ClausesDB.Createclause.OnConflictclause.Columnclause.AssignmentColumnsclause.Assignmentsgorm.Exprgo MIT-0 · 2026-08-17
- gorm.io/gorm v1.31.2: Measure association loading, filtering, creation, and deletion behavior in GORM 1.31.2 with the pinned in-memory SQLite driver 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. HOWgorm.OpenDB.PreloadDB.JoinsDB.WhereDB.FindDB.DeleteDB.CreateDB.SelectDB.Omitclause.Associationsgo MIT-0 · 2026-08-17
- gorm.io/gorm v1.31.2: Keep a tenant scope from being bypassed by an ungrouped Or while inspecting GORM DryRun SQL 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. HOWgorm.Opensqlite.Newgorm.Config.DryRungorm.Config.DisableAutomaticPingDB.ScopesDB.WhereDB.OrDB.Findgo 1.26 MIT-0 · 2026-08-17
- gorm.io/gorm v1.25.7 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-08-19