Skip to content

Report bounded phase and step timings for history failures - #1617

Open
frahlg wants to merge 2 commits into
masterfrom
codex/writer-phase-steps-20261013
Open

frahlg wants to merge 2 commits into
masterfrom
codex/writer-phase-steps-20261013

Conversation

@frahlg

@frahlg frahlg commented Oct 13, 2026 •

Copy link
Copy Markdown
Member

Live-history and forecast failures report total phase time, which can combine many short steps. Archive and rollup failures can return only context deadline exceeded, leaving connection, preparation, lock waits and writes indistinguishable.

Add the longest step and step count to the existing bounded phase timer. Use that timer for archive connection, busy-timeout setup, BEGIN, preparation, archive-view lock, writer lock, write and commit. Capture failures before rollback, busy-timeout restoration and connection close. The phases retain the twelve-slot limit and contain no new sample values, SQL parameters or batch IDs. A phase can contain several SQL operations.

This adds diagnosis. It does not establish the field timeout's cause or change SQL, deadlines, FULL sync, queues, retry rules or cleanup order. The home box still runs the published beta; native merge, release and update remain with the assigned release thread.

Validation:

  • Five real SQLite deadline cases fail for missing phase fields on exact published source f4bfff6991704bd454e94d5c831b62e69d8830bd and pass after the change. They check connection, preparation, both locks and write, preserved committed rows, no SQL contents in the timing fields, and a successful retry.
  • Three race runs pass for these cases and the existing live-write cancellation, repeated-step and lock-wait regressions.
  • Full make verify passes.
  • All 17 CI checks pass or skip as intended on f6ba8176; test run 38495649707 binds the exact head. The earlier automated review applies only to d39a1fe.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 13, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-13T19:24:12.156240Z d39a1fe PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@frahlg frahlg changed the title fix: report longest phase step and count on storage failures Report bounded phase and step timings for history failures Oct 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant