You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After investigating this error a bit, I'd like to understand why the error is raised in the case of:
swift files not empty
status is successful
stdout is empty
stderr is empty
Sadly I can't reproduce this case locally, as stderr is never empty for me, but I think we could handle this case more gracefully than raising an Error. The danger-ruby-swiftlint gem is handling this case by just returning an empty hash, i.e. no issues to report.
I agree with you: we should not fail builds if the output of the command is empty. If you're up for creating the PR, that would be great 😃
If not, let me know and I'll have a look in the coming days.
Hi 👋🏻 Lately, we are increasingly seeing the following error message when running SwiftFormat using this Danger plugin.
After investigating this error a bit, I'd like to understand why the error is raised in the case of:
status
is successfulstdout
is emptystderr
is emptySadly I can't reproduce this case locally, as
stderr
is never empty for me, but I think we could handle this case more gracefully than raising an Error. Thedanger-ruby-swiftlint
gem is handling this case by just returning an empty hash, i.e. no issues to report.https://github.com/ashfurrow/danger-ruby-swiftlint/blob/master/lib/danger_plugin.rb#L167-L169
Do you think we could follow this approach?
The text was updated successfully, but these errors were encountered: