Christian Kreibich f97a33e14d Fix type clash fatal error with log filters that use $ext_func and $include/$exclude ... The logging manager's Manager::TraverseRecord(), called when adding a log filter to a stream, skipped any fields intoduced by a filter's $ext_func when such fields weren't mentioned in a $include restriction or mentioned in an $exclude restriction. This was inconsistent with Manager::RecordToFilterVals, used when actually writing log entries, which does include those values. The result was that the record indices descent in Manager::RecordToFilterVals expects to find only record values, when in fact only the record provided by ext_func is present. This leads to type mismatches and hard Zeek exits like this one: 1300475173.475401 fatal error in zeek/share/zeek//base/init-bare.zeek, line 4810: Val::CONVERTER (string/record) (zeek) The fix makes ext_func's field additions decisive, meaning the filter's include/exclude lists don't apply to it. If a user really wants to override this, they can reset the filter's ext_func back to our no-op default. The included btest produces the above error when the fix is not present.		2020-11-10 18:13:16 -08:00
..
base	Fix type clash fatal error with log filters that use $ext_func and $include/$exclude	2020-11-10 18:13:16 -08:00
policy	dump-events: try to make baseline work on all systems	2020-10-15 15:35:51 +00:00
site	Update site/local.zeek compatibility test	2020-07-27 12:05:10 -07:00
check-test-all-policy.zeek	GH-239: Rename bro to zeek, bro-config to zeek-config, and bro-path-dev to zeek-path-dev.	2019-05-01 21:43:45 +00:00