cp/mktemp: handle closed stdout errors for GNU compatibility#10494
Draft
ChrisDryden wants to merge 5 commits into
Draft
cp/mktemp: handle closed stdout errors for GNU compatibility#10494ChrisDryden wants to merge 5 commits into
ChrisDryden wants to merge 5 commits into
Conversation
|
GNU testsuite comparison: |
|
GNU testsuite comparison: |
… BrokenPipe handling
|
GNU testsuite comparison: |
|
GNU testsuite comparison: |
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.
This is an in progress PR that I am publishing to give an example in the comments in the other PR's how we can use the signal handling changes in the init_data section to handle the stdout error handling the same way the GNU utilities handle it. Just need to fix the windows issues and add more integration testing.