Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upbpo-35182: fix communicate() crash after child closes its pipes #18117
Conversation
This comment has been minimized.
This comment has been minimized.
the-knights-who-say-ni
commented
Jan 22, 2020
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA). CLA MissingOur records indicate the following people have not signed the CLA: For legal reasons we need all the people listed to sign the CLA before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. If you have recently signed the CLA, please wait at least one business day You can check yourself to see if the CLA has been received. Thanks again for the contribution, we look forward to reviewing it! |
d3ae95e
into
python:master
This comment has been minimized.
This comment has been minimized.
miss-islington
commented
Jan 22, 2020
This comment has been minimized.
This comment has been minimized.
miss-islington
commented
Jan 22, 2020
I'm having trouble backporting to |
This comment has been minimized.
This comment has been minimized.
miss-islington
commented
Jan 22, 2020
Sorry, @alpire and @gpshead, I could not cleanly backport this to |
This comment has been minimized.
This comment has been minimized.
miss-islington
commented
Jan 22, 2020
This comment has been minimized.
This comment has been minimized.
miss-islington
commented
Jan 22, 2020
Sorry @alpire and @gpshead, I had trouble checking out the |
This comment has been minimized.
This comment has been minimized.
miss-islington
commented
Jan 22, 2020
This comment has been minimized.
This comment has been minimized.
miss-islington
commented
Jan 22, 2020
Sorry, @alpire and @gpshead, I could not cleanly backport this to |
…pythonGH-17020) (pythonGH-18117) When communicate() is called in a loop, it crashes when the child process has already closed any piped standard stream, but still continues to be running Co-authored-by: Andriy Maletsky <andriy.maletsky@gmail.com>. (cherry picked from commit d3ae95e) Co-authored-by: Alex Rebert <alex@forallsecure.com>
This comment has been minimized.
This comment has been minimized.
bedevere-bot
commented
Jan 23, 2020
GH-18148 is a backport of this pull request to the 3.8 branch. |
…pythonGH-17020) (pythonGH-18117) When communicate() is called in a loop, it crashes when the child process has already closed any piped standard stream, but still continues to be running Co-authored-by: Andriy Maletsky <andriy.maletsky@gmail.com>. (cherry picked from commit d3ae95e) Co-authored-by: Alex Rebert <alex@forallsecure.com>
This comment has been minimized.
This comment has been minimized.
bedevere-bot
commented
Jan 23, 2020
GH-18151 is a backport of this pull request to the 3.7 branch. |
…GH-18117) (GH-18148) When communicate() is called in a loop, it crashes when the child process has already closed any piped standard stream, but still continues to be running Co-authored-by: Andriy Maletsky <andriy.maletsky@gmail.com>. (cherry picked from commit d3ae95e) Co-authored-by: Alex Rebert <alex@forallsecure.com> https://bugs.python.org/issue35182
…GH-18117) (GH-18151) When communicate() is called in a loop, it crashes when the child process has already closed any piped standard stream, but still continues to be running Co-authored-by: Andriy Maletsky <andriy.maletsky@gmail.com>. (cherry picked from commit d3ae95e) Co-authored-by: Alex Rebert <alex@forallsecure.com> https://bugs.python.org/issue35182 Automerge-Triggered-By: @gpshead
alpire commentedJan 22, 2020
•
edited
When communicate() is called in a loop, it crashes when the child process has already closed any piped standard stream, but still continues to be running. The fix is trivial.
(Original PR is #17020. I had to create a new one to rebase on top of master & fix merge conflicts)
https://bugs.python.org/issue35182