Closed readevalprint closed 10 years ago
Nasty issue to have, as I believe we have no way to know what was written on the pipe (and therefore known where to resume the write). The issue is still on master but the string asks to report this issue on googlecode, so this code must not be the most recent. We are going to dig into it to see how we can handle this (and the possible performance impact to write the message byte per byte).
Thanks @thomas-mangin
Ok - I the error message is confusing as errno 4 is errno.EINTR - which just mean we should retry. Should be cleanly fixed with 65c48d172df6253d8070cdfdf605cee335732725
Nice!
I'm not sure about the fix for this. Perhaps in the case of this specific error we could retry a few times before raising the exception?