1274136 - Subprocess pipe close() can reject if pipe is already closed

Status: NEW

(Toolkit :: Async Tooling, defect)

Description

[Andrew Swan [:aswan]]

If a pipe to(/from) a subprocess is already closed, calling close() can throw because the closed pipe is not present in the worker's pipe id map (this applies to Unix, I haven't looked at the Windows code to see if it has a similar issue).

The documentation for close() doesn't mention that it can reject.  Moreover, it is a pain for users of subprocess to either carefully track when the pipe is closed or always catch close results and look for the eof error, if subprocess could handle this internally that would be cool...