"EAGAIN: resource temporarily unavailable, write" on fatal

[allevo]

Before #730, the use of fatal was safe.
After that version, my application crash with EAGAIN: resource temporarily unavailable, write.

The linked lines live in sonicboom repo:

https://github.com/mcollina/sonic-boom/blob/e1b31fb93c5a8c306cdc16021e81b4995056a5aa/index.js#L245-L248

This behaviour was considered a patch but the behaviour changes.

Can I may send a PR with a patch (maybe a configuration flag)?

[mcollina]

Sure thing Il 11 nov 2019, 10:25 +0000, Tommaso Allevi <notifications@github.com>, ha scritto:

…

Before #730, the use of fatal was safe. After that version, my application crash with EAGAIN: resource temporarily unavailable, write. The linked lines live in sonicboom repo: https://github.com/mcollina/sonic-boom/blob/e1b31fb93c5a8c306cdc16021e81b4995056a5aa/index.js#L245-L248 This behaviour was considered a patch but the behaviour changes. Can I may send a PR with a patch (maybe a configuration flag)? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.