Dominik Charousset
Dominik Charousset
We can most likely increase the performance of forwarding decisions by using a radix tree for storing peer filters. Currently, the `core_actor`/`stream_governor` simply stores all filters as `vector` and iterates...
Leftover todo item from https://github.com/zeek/broker/pull/219. A JSON schema is mostly for documentation purposes, but we could also use the schema to verify our messages in the `btest` suites to add...
Thanks to @ckreibich for bringing this up. It seems like the new connector does not distinguish between recoverable errors (remote side does not exist) and fatal errors (incompatible peer /...
Currently, users create an `endpoint` directly by calling its constructor. However, creating an `endpoint` can fail for several reasons. The same is true for `configuration`. In https://github.com/zeek/broker/pull/81#issuecomment-575914374, we've discussed this...
As outlined in https://github.com/zeek/broker/pull/160, Broker currently serializes data using `caf::binary_serializer` and `caf::binary_deserializer` in its backends. This is unsafe, because the binary format may change between CAF releases. This means any...
Masters and clones no longer use direct actor-to-actor communication after redesigning store communication in the ALM branch. Instead, the new channel abstraction enables them to communicate over the pub/sub layer....
Related to #125: if clones run into errors that it can't recover from (e.g., losing command messages or the master's endpoint goes down), it shall try to re-attach to the...
Note: changes have been automatically generated from `clang-tidy`. Relates #249.
For context, the original issue was reported by @simeonmiteff here: https://github.com/zeek/broker/issues/345. He found that Broker is dropping "holes" in vectors when doing something like this: ``` local v: vector of...