Currently we only search the message field. We should be able to filter based on service or on type as well.

They should take single matcher during construction, and their match method should take a generic range, using the new generic matcher support.

Expected usage:

REQUIRE_THAT(get_keys(), AllMatch(KeyPattern({1, 2, 3})));
REQUIRE_THAT(get_numbers(), NoneMatch(IsOdd{}));
REQUIRE_THAT(get_strings(), AnyMatch(Contains("webscale") && !Contains("MongoDB")));

the matching semantics

What steps did you take and what happened:
I was testing Azure snapshot support, and making sure that things worked fine with AZURE_RESOURCE_GROUP omitted when backing up without snapshots, and that with snapshots, things worked properly with it set, and we were seeing appropriate error messages with it either unset or set to a bad value (wrong group or invalid group).

What I think I'm see

I think we should patch test/CMakeLists.txt to always use -Wall -Werror on *nix and the corresponding MSVC flags. It is way too easy to overlook a warning in the CI output as #1797 has shown.

@nlohmann Thoughts?

Hello,

We are using this module for the cluster creation for our project. We are planning to use some of our applications to be running with confidential computing. I didn't notice that support yet by this module. Could you please enlighten, in case you have some plan in near future.
Any response on this topic will be well appreciated !

Thanks,
Sudip

Just lost my status screens with few billions of execs :(
So, my ideas:

1. Can we store all the fuzzer stats as shown in status screen, and then restore it when resuming (with both AFL_AUTORESUME and '-i' option) ? If it somehow affects or depends on inner state of AFL++ instance, can we restore this inner state too?
2. Can we prevent random Ctrl+C presses for example, by asking to confirm? You

Context: https://twitter.com/bwplotka/status/1334404169432788992

Help wanted 🤗