JuliusBrussee/caveman · error
forget: %w
Error message
forget: %w
What it means
The DELETE of the target memory row failed inside the Forget transaction after lineage pointers were staged for repair. The wrapped error is the SQLite delete failure; rollback undoes the repairs.
Source
Thrown at mem/store.go:357
}
if supersedes.Valid {
if _, err := tx.Exec(
`UPDATE memories SET superseded_by = ? WHERE id = ?`,
nullableLineageID(supersededBy), supersedes.String,
); err != nil {
return false, fmt.Errorf("repair forgotten predecessor: %w", err)
}
}
if supersededBy.Valid {
if _, err := tx.Exec(
`UPDATE memories SET supersedes = ? WHERE id = ?`,
nullableLineageID(supersedes), supersededBy.String,
); err != nil {
return false, fmt.Errorf("repair forgotten successor: %w", err)
}
}
if _, err := tx.Exec(`DELETE FROM memories WHERE id = ?`, id); err != nil {
return false, fmt.Errorf("forget: %w", err)
}
if err := tx.Commit(); err != nil {
return false, fmt.Errorf("forget commit: %w", err)
}
return true, nil
}
func nullableLineageID(value sql.NullString) any {
if value.Valid {
return value.String
}
return nil
}
// Count returns the number of durable memory blocks without loading their
// contents. Callers omit this number on error rather than presenting zero.
func (s *Store) Count() (int, error) {
var count intView on GitHub (pinned to 766dce6b13)
Solutions
- Retry the forget
- Inspect the wrapped sqlite error (locks, disk)
Defensive patterns
Strategy: try-catch
When it happens
Trigger: Thrown at mem/store.go:357 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of JuliusBrussee/caveman@766dce6b13 (2026-08-18).
Data as JSON: /api/errors/7467698e2a5fbaa0.
Report an issue: GitHub.