-
Notifications
You must be signed in to change notification settings - Fork 16
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
On error log STDOUT if STDERR is empty #45
On error log STDOUT if STDERR is empty #45
Conversation
Re: the rubocop comment, I tried presence first but it isn't available and I didn't feel like pulling in active_support just for this |
👍 |
I didn't realized we owned AwesomeSpawn, lol. |
@djberg96 yup so it is even more awesome than you thought 😄 |
@agrare Isn't
|
Yep, I think it is, so you'll have to check using |
Hm specs pass:
|
If a process doesn't correctly log to STDERR then the default .run! log message isn't very helpful. This logs command_result.error if it is present, otherwise it logs command_result.output.
3e19868
to
a17cba3
Compare
Okay checking for .nil? || .empty? just to be safe |
Checked commit agrare@a17cba3 with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0 lib/awesome_spawn.rb
|
My guess is that it's being pulled in by the |
If a process doesn't correctly log to STDERR then the default .run! log
message isn't very helpful. This logs command_result.error if it is
present, otherwise it logs command_result.output.