Paul Loyd

Yep, it's a case for blocking requests (`ctx.request(..).resolve().await`). But in the case of non-blocking requests, all responses are handled using a mailbox in the typical main loop, so there is...

It seems much better to write in `spawn_blocking` like in the dumper.

I'm sorry for not getting back to you sooner. An actor group cannot contain actors across multiple nodes, but each node can have a group with the same name and...

> found this one to be the best suited for my purpose Thank you for your interest in the project! Feel free to ask anything; I know that the documentation...

@qwfy Thanks for your thoughts! You mentioned common and essential issues in message-passing systems. On the rights of "just brainstorming" (so feel free to ignore it), I would like to...

> More and more PRs are merged, but nobody cares about maintaining the API documentation. I agree; we need to force the creation of documentation for all new extensions. But...

This crate should support all three under features, so I'd like to accept PR. Anyway, I'm thinking about moving to jiff for my production code so that it will be...

+1, I'd like to rename `Requests` to `Message Rate` because not all messages are requests.

@apsaltis Hm, I think it's easy to implement `clickhouse::serde::uuid::vec` in the same way as `serde::uuid::option`. It looks clumsy; I'm sure there is a better approach here by changing ```rust pub...

@keltia, would you like to open a separate issue? The client should generate a different subset of field names for serialize and deserialize processes. Now, it skips it in both...