This commit switchexisd the Raw reader to use posix_spawn, instead of
the combination of fork + exec. This should be much more efficient, and
also makes the code smaller, and easier to read and understand.
* origin/topic/timw/3184-modbus-extensions:
Pass parsed file record information with ReadFile/WriteFile events
Add length field from header to ModbusHeaders record type
Modbus: Add support for Encapsulation Interface Transport (FC=2B) requests and responses
Modbus: Add support for Diagnostics (FC=8) requests and responses
* origin/topic/timw/3184-modbus-extensions:
Pass parsed file record information with ReadFile/WriteFile events
Add length field from header to ModbusHeaders record type
Modbus: Add support for Encapsulation Interface Transport (FC=2B) requests and responses
Modbus: Add support for Diagnostics (FC=8) requests and responses
* origin/topic/timw/cmake-find-package:
Change VERSION variable in CMake config to ZEEK_VERSION_FULL
Update bifcl and binpac for FindPackage fixes
Remove usage of FindRequiredPackage
Update zeekctl and cmake to deprecate FindRequiredPackage
Update broker submodule for pybind11 + cmake changes
Failing currently with:
Failed to start an instance! Failed to pull null image! Repository does not exist or may require authentication.
Container errored with 'ImagePullBackOff: Back-off pulling image "gcr.io/cirrus-ci-community/zeek/zeek/ci/centos-7/dockerfile:a0c25357a3a7dc08f6c1e61e6f81ad36"'
This is based on the discussion in zeek/zeek#2668. Using &default with tables
can be confusing as the default value is not inserted. The following example
prints an empty table at the end even new Service records was instantiated.
type Service: record {
occurrences: count &default=0;
last_seen: time &default=network_time();
};
global services: table[string] of Service &default=Service();
event zeek_init()
{
services["http"]$occurrences += 1;
services["http"]$last_seen = network_time();
print services;
}
Changing above &default to &default_insert will insert the newly created
default value upon a missed lookup and act less surprising.
Other examples that caused confusion previously revolved around table of sets
or table of vectors and `add` or `+=` not working as expected.
tbl_of_vector["http"] += 1
add tbl_of_set["http"][1];
This is similar to GH-3206. There do not seem to be practical
consequences - but we should still fix it.
This also includes the udp-testcase that was forgotten in GH-3206.
There's something going on with the image cache on Cirrus where the images
are sometimes vanishing from the cache, thus causing builds to fail
because it can't load them. This forces a rebuild of all of the images,
thus refreshing the cached version of all of them.
This marks every identifier used within an attribute as seeds. The scenario
this avoids is functions referenced through attributes on unused tables or
record types (&default, &expire_func, ...) being dinged as unused as
that's rather confusing.
Also adds test for the above and a light smoke test into language/ as it
doesn't appear we had coverage here.
Closes#3122
* origin/topic/vern/zam-memory-reduction:
Baseline "-a zam" update
increase BTest wait time to abide ZAM compilation times
avoid script coverage overhead (especially memory) when using ZAM
fixes for correctly tracking which functions have been fully inlined
support for discarding ASTs once compiled via ZAM script optimization
some code simplifications and streamlining
