This ignores the SIGPIPE signal on the calling thread. This signal can be fired when trying to write() to a pipe that's being closed or while closing a pipe that's being written to. We can run into that situation so we ignore this signal and continue as normal. As a side note for this implementation, it would be great if we could safely restore the sigmask, but unfortunately the operation of resto
source not stored for this graph (policy: none)