Skip to content
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

Parsing stops abruptly in german log #102

Closed
baubakg opened this issue May 20, 2024 · 0 comments · Fixed by #103
Closed

Parsing stops abruptly in german log #102

baubakg opened this issue May 20, 2024 · 0 comments · Fixed by #103
Labels
bug Something isn't working
Milestone

Comments

@baubakg
Copy link
Member

baubakg commented May 20, 2024

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
@baubakg baubakg added the bug Something isn't working label May 20, 2024
baubakg added a commit that referenced this issue May 21, 2024
@baubakg baubakg mentioned this issue May 21, 2024
6 tasks
@baubakg baubakg linked a pull request May 21, 2024 that will close this issue
6 tasks
baubakg added a commit that referenced this issue May 21, 2024
baubakg added a commit that referenced this issue May 21, 2024
* #102 reproduced issue

* Fixing #102 we now use a Buffered reader so that the test no longer fails

* Fixing #102 updating release notes
@baubakg baubakg added this to the 1.0.9 milestone May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant