Skip to content
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

standard output is truncated using node v6 #519

Closed
75lb opened this issue May 12, 2016 · 8 comments

Comments

@75lb
Copy link

commented May 12, 2016

using node v6, the output from standard is only partially logged to stdout.. it's caused by the new process.exit() behaviour.

for now, i can get the full output by piping to a file or pbcopy.

@feross

This comment has been minimized.

Copy link
Member

commented May 12, 2016

Wow, that's unfortunate.

@75lb

This comment has been minimized.

Copy link
Author

commented May 15, 2016

one work-around to this new node v6 behaviour is to replace process.exit() calls with

process.exitCode = 1
return 

This allows the process to exit gracefully, without losing any buffered IO, but ironically causes standard to fail every time due to #510 .

@feross

This comment has been minimized.

Copy link
Member

commented May 16, 2016

There's discussion of fixing this bug in Node v6 here: nodejs/node#6456

feross added a commit to standard/standard-engine that referenced this issue May 16, 2016

@feross

This comment has been minimized.

Copy link
Member

commented May 16, 2016

Turns out this was a pretty easy fix in standard-engine.

standard/standard-engine#108

@75lb If you npm rm standard && npm install standard in a few minutes you should get the fix.

@75lb

This comment has been minimized.

Copy link
Author

commented May 16, 2016

confirmed.. cheers brother 👍

@feross

This comment has been minimized.

Copy link
Member

commented May 16, 2016

Cheers 🍻

@Flet

This comment has been minimized.

Copy link
Member

commented May 17, 2016

Wow this is good info to know regarding v6...

@feross

This comment has been minimized.

Copy link
Member

commented May 17, 2016

@Flet Yeah... hoping they find a way to keep writes to stdout async but flush the pending data before exit.

@lock lock bot locked as resolved and limited conversation to collaborators May 10, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
3 participants
You can’t perform that action at this time.