Skip to content

SQLite failures hide actionable error details #36578

Closed as not planned
Closed as not planned

Description

@bvolpato

Description

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

  1. github-actions commented on Sep 11, 2026

    @github-actions
    Contributor

    To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions