We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Given a specific file the log parser bruptly stops parsing wwith no error.
The problem is because the file is marked as UTF-8 it seems, but there are non-UTF-8 characters in the file issue102_charSetBadUTFChar.log
Example is if you perform SED :
sed 's/nms/RND1/g' issue102_charSetBadUTFChar.log tissue102_charSetBadUTFCharNew.log
you get the error:
sed: RE error: illegal byte sequence
The text was updated successfully, but these errors were encountered:
#102 reproduced issue
e9fbe91
Fixing #102 we now use a Buffered reader so that the test no longer f…
35452a9
…ails
Fixing #102 updating release notes
fb6b0cc
#102 reproduced issue (#103)
f7a841a
* #102 reproduced issue * Fixing #102 we now use a Buffered reader so that the test no longer fails * Fixing #102 updating release notes
Successfully merging a pull request may close this issue.
Given a specific file the log parser bruptly stops parsing wwith no error.
The problem is because the file is marked as UTF-8 it seems, but there are non-UTF-8 characters in the file
issue102_charSetBadUTFChar.log
Example is if you perform SED :
sed 's/nms/RND1/g' issue102_charSetBadUTFChar.log tissue102_charSetBadUTFCharNew.log
you get the error:
The text was updated successfully, but these errors were encountered: