-
Notifications
You must be signed in to change notification settings - Fork 47
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
Invalid error message alignment #63
Comments
v4 includes tons of changes (was pretty much a complete rewrite), so could you please try it again with the latest version of the step @koral-- ? |
@koral-- thanks for the report & screen shot! Re:
That's not the fault of the step directly, it affects Bitrise logs sometimes if stdout and stderr are both written at about the same time on Linux. We're still searching for exactly what might cause this, and we only saw this happening on Linux; most likely some kind of stderr buffering delay is the root cause as technically we just use Go's built in "Combined Output" method, which returns both the stdout and stderr in the same string/buffer. That issue is tracked at bitrise-io/bitrise#546 (was also reported by you ;) ), so I'll close this issue here, but feel free to comment if we missed anything and we'll reopen it :) |
The last warning is red, while fatal error is white.
It seems that first line of the output from 3rd attempt is printed red as an overall result and the next line is not coloured.
Maybe all the overall error message should be red?
Screenshot contents is produced by version 3.5.1 of the step however, I haven't found anything related in release notes at: https://github.com/bitrise-io/steps-git-clone/releases
The text was updated successfully, but these errors were encountered: