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
While ESLEvent works fine with normal events, it is possible to receive log events with no channel UUID, leaving the User-Data header blank. They look like:
The User-Data line is 'User-Data: \n', including a space. Both the newline and space are stripped, and you end up with this (pretty-printed header dict) where User-Data is considered a continuation of the previous header:
While ESLEvent works fine with normal events, it is possible to receive log events with no channel UUID, leaving the User-Data header blank. They look like:
The User-Data line is
'User-Data: \n'
, including a space. Both the newline and space are stripped, and you end up with this (pretty-printed header dict) where User-Data is considered a continuation of the previous header:Removing the whitespace strip from ESLEvent.parse_data() doesn't seem to have any adverse affects on other events and fixes this issue:
The text was updated successfully, but these errors were encountered: