When you use minio or another S3 provider that uses path_style for buckets and
do not configure this with the force_path_style then logstash while fail with
a stacktrace which contains the S3 secret key. This was tested with secret key
and key identifier present in the config. Not tested with a config file yet.
probably config file is better.

ActorAdapter will ignore null message with "Adapter function returned null which is not valid as an .."

However, this seems not be documented. For instance, scaladoc/javadoc of pipeToSelf could mention it as well as any other place where adapters are used.

Summa

A broken config file can easily crash the program. Nuclear should be able to detect this problem and either reset the config, or fix the broken parts. Somewhere within the code that loads the config should be a try-catch block that does this.

it's becoming more time-consuming and error-prone to manually re-test all the demos following internal refactorings and API adjustments.

now that the API is fleshed out a bit, it's possible to test a large amount of code (non-granularly) without having to simulate all interactions via Puppeteer or similar.

a lot of code can already be regression-tested by simply running all the demos and val