-
-
Notifications
You must be signed in to change notification settings - Fork 91
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
Continuous import of Zeek logs in VAST is broken #750
Conversation
bae5873
to
64e100f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you got the interface for fdinbuf
right, but i'd like to change line_range
to make it more usable.
BTW, this is looks almost finished to me. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is looking good. The feedback by @tobim needs to be addressed, though.
The zeek reader would always try to read up to slice_size events from the input stream. For a continous stream that did not have that many events, the reader would block indefinitely until either more events arrive or the stream was closed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
It feels like a changelog entry should document the bugfix. |
No description provided.