On Mon, 21 Jul 2025 at 12:26, Dennis Luehring via Boost < boost@lists.boost.org> wrote:
the statemachine of the user code bases on the fact that a handler of an async_write needs to always comes before the handler of an async_read
i don't think that is guaranteed, is it?
<snip>
is it possible that the async_write handler comes after the async_read handler?
Yes, that used to be a bug in Boost.Redis. Quoting the Changelog entry [1] Under load and on low-latency networks it is possible to start receiving
responses before the write operation is completed and while the request is still marked as staged and not written. This messes up with the heuristics that classifies responses as unsolicited or not.
[1] https://github.com/boostorg/redis/blob/76129bbcb8373f23d37877fccededb288690e...