Dominik Charousset

> Could these please be addressed? Eventually. We currently don't run any C++20 build in our CI. I'd be happy to merge a PR, though. 😉

Btw, I've played a bit with that recently and it's quite annoying. If you do `[=, this]`, you actually get warnings in C++17 mode about redundant capture. So there's no...

Alternatively, we provide only `actor` and `typed_actor` overloads for inserting into the registry and then store the interface along the (strong) pointer.

The metrics that come from CAF code (the process metrics also come from CAF) probably need to wait for CAF 0.19, the Broker metric I can update right away.

Yep, thanks for the pointer. That one fell off the radar as it seems. I'm not sure if there's anything we can do about it, as the stack trace indicates...

Putting this as a reminder here, also probably for after 5.0 since it's just a 'nice-to-have': - Provide a JSON schema for the new WebSocket protocol.

> Revisit need for Python bindings. With WebSockets available in 5.0 as language-agnostic way to communicate to Broker: why not deprecate the bindings with 5.0? We currently have 6 tickets...

> That also allows the Python bindings to remain not-deprecated for the 5.0 LTS cycle, giving people plenty time. Just for my understanding: what difference does it make to deprecate...

> Check whether we can disable any warnings from CAF. That one is probably tricky, because we are building CAF as part of Broker. Hence, only suppressing warnings from CAF...

> do you happen to have any quick explanation for that behavior or whether there's anything Broker can do about it? CAF won't close network connections on its own. It...