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
Raw log lines such as --------- beginning of system will be displayed as part of the previous log line's message.
When reading log from stdin pipe, it's not possible to identify when a log line ends.
This is because sys.stdin.readline() ignores empty lines which are what the Long format uses to indicate a log line ended.
We can only be certain for sure that a log line ended whenever a new one starts.
So, raw log lines between them will not be considered as such.
When reading log from live device, we can properly identify the end of the log line but this is not done in order to keep the code simple, it's not worth the trouble right now.
The text was updated successfully, but these errors were encountered:
TBM13
changed the title
Long Format: Raw lines are interpreted as part of the previous line's message
Long Format: Raw lines interpreted as part of the previous line's message when reading log from file
Nov 23, 2023
TBM13
changed the title
Long Format: Raw lines interpreted as part of the previous line's message when reading log from file
Long Format: Raw lines interpreted as part of the previous line's message
Nov 23, 2023
Raw log lines such as
--------- beginning of system
will be displayed as part of the previous log line's message.When reading log from stdin pipe, it's not possible to identify when a log line ends.
This is because sys.stdin.readline() ignores empty lines which are what the Long format uses to indicate a log line ended.
We can only be certain for sure that a log line ended whenever a new one starts.
So, raw log lines between them will not be considered as such.
When reading log from live device, we can properly identify the end of the log line but this is not done in order to keep the code simple, it's not worth the trouble right now.
The text was updated successfully, but these errors were encountered: