Repository navigation
Fix large command results failing Turn persistence - #17
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Command completion snapshots above 512 KiB were accepted by the 4 MiB Runtime transport but rejected by the execution journal, failing the Turn after streamed command output had already been saved. Align the journal payload ceiling with the existing transport limit and store large observations alone, preserving per-Turn budgets and failure semantics.
Add payload-free journal failure categories, SQLSTATE and correlation IDs, plus regression coverage for large second-turn snapshots, database failures and retained history. The historical Weibo failure is consistent with this defect, but its rejected event and original error were not retained.
Validation: affected Go packages,
make check-runtime-contract, dedicated local PostgreSQL regressions (including real JSONB failure), diagnostic redaction tests, bilingual documentation checks, and independent review passed. No paid production replay was performed.