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
I've started using pipecolor with the unit-test log output from the project I work on, and it's great.
However, in one scenario the output cuts off early with the message Error: stream did not contain valid UTF-8. I made sure this only happens when piping through pipecolor, so the message is not coming from our code.
It appears that something in a test of ours is writing some binary data to the log; so pipecolor is correct that there's invalid UTF-8 in the stream. However, it should not give up when this happens; it should just write the offending line as-is and go on to the next one. Otherwise it ends up hiding information from the user.
(PS: I'm running the latest version of pipecolor, built via cargo, on macOS 12.6.5.)
The text was updated successfully, but these errors were encountered:
I've started using pipecolor with the unit-test log output from the project I work on, and it's great.
However, in one scenario the output cuts off early with the message
Error: stream did not contain valid UTF-8
. I made sure this only happens when piping through pipecolor, so the message is not coming from our code.It appears that something in a test of ours is writing some binary data to the log; so pipecolor is correct that there's invalid UTF-8 in the stream. However, it should not give up when this happens; it should just write the offending line as-is and go on to the next one. Otherwise it ends up hiding information from the user.
(PS: I'm running the latest version of pipecolor, built via cargo, on macOS 12.6.5.)
The text was updated successfully, but these errors were encountered: