Dmitriy Kovalenko 3d6428510f Warn users when SQLite diagnostic log writes fail (#47887) ...

## Why

Failed SQLite writes leave diagnostic logs incomplete. Notify users before they close Codex so they can submit logs or run `codex doctor`.

## What changed

- Add a best-effort warning on the first log write failure in standalone and in-process app servers, while continuing to retain failure diagnostics in memory.
- Handle failures that occurred before the in-process warning reporter was attached.
- Tailor the warning's guidance to whether submitting logs is enabled.

## Testing

Add coverage for warning deduplication, both guidance variants, retained diagnostics after the notification sender is dropped, and SQLite flush failures before and after reporter attachment. Extend log upload integration coverage and add a TUI warnings snapshot.

GitOrigin-RevId: 12a74126d13c3568430e539a180cca47fa931fa9

2026-09-24 17:04:50 +00:00

..

goals_migrations

Preserve thread context when retrying or editing turns (#33211)

2026-07-15 02:35:49 +00:00

logs_migrations

Align SQLite feedback logs with feedback formatter (#13494)

2026-03-18 22:44:31 +00:00

memory_migrations

Add memory dual writing and v2 readiness reporting (#43827)

2026-09-08 14:23:23 +00:00

migrations

Clean up legacy Guardian thread metadata in SQLite (#47303)

2026-09-22 15:05:27 +00:00

queue_migrations

Dispatch queued messages written by other processes (#39034)

2026-08-17 17:19:46 +00:00

src

Warn users when SQLite diagnostic log writes fail (#47887)

2026-09-24 17:04:50 +00:00

thread_history_migrations

Preserve and expose thread item lifecycle timestamps (#47114)

2026-09-21 22:23:26 +00:00

BUILD.bazel

Shard state unit tests under Bazel (#37478)

2026-08-07 17:49:48 +00:00

Cargo.toml

Avoid building a host SQLite driver for SQLx macros (#47084)

2026-09-21 18:30:31 +00:00