Jay
How about setting a larger capacity?
Setting a larger capacity is to get around the CI issues. In fact, the thread pool should not be created by the library, it should be a builder parameter given...
Hi, do you have an example shows the problem?
It seems that cancel is not called on `ClientSStreamReceiver`. /cc @overvenus
/cc @brson @Little-Wallace @lucab
> can the thread-group logic be folded into `FailScenario`? `FailGroup` can be accessed via a global fuction, so it may not be appropriate to use `FailScenario` directly. But I think...
Process isn't compatible with the default test runner.
No, it's not valid anymore. We can start migrating the c code to rust.
Or the library can expose the `FailPointRegistry` to users, so users can control the lock pattern more precisely.
One coroutine to one transaction is a more reasonable mapping to me.