Repository navigation
Preserve finite file-limit signal handling in 0.2.27 - #39
Merged
Merged
Conversation
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
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.
Trusted Codex and Claude CLI processes could terminate with
SIGXFSZwhen Python restored an inherited ignored signal under a finite POSIX file-size limit. Preserve the inherited disposition in that launch condition so an oversized write can returnEFBIGwhile the kernel limit stays enforced. Unlimited parents, default signal dispositions and the separate untrusted command executor retain subprocess defaults. Process cleanup and typed outcome checks remain intact.Prepare 0.2.27 metadata, release notes and all 448 canonical Studio captures. The original offending write and file remain unidentified. This change grants no additional attempt or budget reset and does not establish successful same-run recovery or generated-product acceptance.
Validation:
The complete exact-head CI suite remains required before merge.