-
Notifications
You must be signed in to change notification settings - Fork 516
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
CLI tool exits immediately instead of reading from STDIN on Cygwin #121
Comments
Hmm... When I comment out the uncaughtException handler in
Googling that leads to nodejs/node-v0.x-archive#6459, so this problem seems to be way outside the scope of Bunyan. Feel free to close the issue; I would be happy if there was some sort of workaround, though. |
Happy to accept a work around PR that doesn't loose the uncaughtException handler facility for other platforms. However, given that this is a node core issue (not supporting cygwin), I'm closing this for now. Sorry I don't have a better answer. |
Apologies in advance if this turns out to be a Cygwin issue, rather than a Bunyan bug.
Running the following simple test program:
Results in this output when run in the Cygwin terminal, and trying to have the
bunyan
CLI tool format the output:It seems like the
bunyan
process exits immediately (after printing the * * *), so the log statement fails to write to STDOUT.FWIW, the same example works just fine in the standard Windows shell on the same machine. Piping the output into something else (like
less
) works fine, too.The text was updated successfully, but these errors were encountered: