Build from Zeek v6.2.0 #9
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Zeek v6.2.0 was recently released. One change in particular I've been waiting to take advantage of in that release is the fix to zeek/broker#316, which I originally reported separately with my own issue at zeek/zeek#3532. I just now generated a Zeek artifact based on this branch in an Actions run and followed the repro steps from zeek/broker#316 to verify that the issue is fixed. Beyond that, it'll just be good to have the latest Zeek bundled with our next set of Brimcap/Zui releases, which I hope to be putting together soon.
In addition to pointing at the new Zeek release tags, the build steps have been adjusted to reflect the changes in zeek/zeek#3576, which I became aware of when doing early verifications of zeek/broker#316 at the request of the Zeek dev team.