During our Internal GREAT FLAKE SHAKE we discovered that sometimes the wds child process will attempt to forward notifications to the parent when the parent is not active. This lead to sparse EPIPE errors being thrown.
The underlying issue of the child forwarding requests to the parent exists, but this at least will avoid any crashing due to uncaught exceptions.
During our Internal GREAT FLAKE SHAKE we discovered that sometimes the wds child process will attempt to forward notifications to the parent when the parent is not active. This lead to sparse
EPIPE
errors being thrown.The underlying issue of the child forwarding requests to the parent exists, but this at least will avoid any crashing due to uncaught exceptions.