You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a session database write fails, the assistant error can be reduced to:
Failed to execute statement
The nested SQLite result is lost through the SQL/Drizzle error wrappers. In an observed failure, the retained internal cause was SQLiteError: database or disk is full, but the session UI and process error did not expose that actionable detail.
Expected behavior
Surface a sanitized SQLite result, for example:
Failed to execute statement: database or disk is full
Do not include SQL query parameters or arbitrary native messages, because SQLite diagnostics can echo bound values.
Additional context
The observed database passed PRAGMA quick_check and resumed writing after the transient failure. The filesystem was under high utilization, supporting SQLITE_FULL rather than corruption.
Activity
github-actions commentedon Sep 11, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.