-
Notifications
You must be signed in to change notification settings - Fork 878
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
flush & flushSync stdout on Node core streams #458
Comments
is this relevant to the v5 release and the sonic-boom approach (cc @mcollina) |
The sonic-boom approach does it correctly. This is more of a problem with the non extreme/sonic-boom approach. We don't have a way to flush stdout. |
yeah that's a node core issue - so it's a wont-fix for us - we recommend using |
@davidmarkclements Fair enough. Though we might want to emphasize this in the docs? |
absolutely - feel welcome to PR against next-major docs |
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. |
Even in non extreme mode logs are not properly flushed during
process.exit
. See, nodejs/node#6456No sure how to resolve this? Should we send a cb to every
write
call to keep aisFlushed
flag up to date?The text was updated successfully, but these errors were encountered: