Eric Traut e8651516f4 Log rollout writer OS errors (#24474) ...

## Why

Refs #24425.

We have seen rollout JSONL corruption that appears consistent with a
rollout write failing after partially appending a line, followed by a
retry that appends the same item again. The available user logs did not
include the underlying OS error, so it is hard to tell whether the
trigger was `ENOSPC`, quota exhaustion, a filesystem error, or something
else.

This PR adds the missing diagnostics for future reports.

## What changed

- Include `ErrorKind` and `raw_os_error()` in rollout writer failure
logs.
- Preserve the existing append-only rollout write path; this PR is
diagnostic-only.

## Verification

- `just test -p codex-rollout`

2026-05-26 10:33:22 +02:00

..

src

Log rollout writer OS errors (#24474)

2026-05-26 10:33:22 +02:00

BUILD.bazel

Extract rollout into its own crate (#15548)

2026-03-24 18:10:53 -07:00

Cargo.toml

[codex] Make thread search case-insensitive (#23921)

2026-05-21 14:14:01 -07:00