Jonas Breuer

~~In general, the async implementation seems to work. There is still one bug somewhere, that causes the CI to be stuck (see https://github.com/aerospike/aerospike-client-rust/runs/3326575266). Please cancel this CI run since it...

Ready to review from my side. I'm a little unsure about the other open PRs. This one moved the whole client to the aerospike-core folder. In theory, git tracked the...

Can you check if there is something cached in your system? This looks like it tries to load the old, sync client.

Fixed. Looks like cargo does not like it when i load member crates as dev dependency. Its now always loading aerospike-macro. For me its compiling correctly now.

@khaf do you have any time plan on when you are going to review this?

Can you give me some more info on the case where you discovered that? I dont really understand whats the point in having multiple runtimes. Normally, that should only be...

First to go back to your original question about the loops: In general this is not a problem of the client. The client itself never starts any runtime. It just...

In general you are right. But i would like to prevent doing that, since it would not really make sense in the rust ecosystem. More exact description of the current...

Found the problem. Now the problem is that the clients retries are too fast. It tries to get a connection from the pool 4 times. After that, the operation fails....

From my side, it depends on if the client should be handling runtimes itself or not. In many cases, there is probably a runtime handler in place. That means that...