The following throws when it shouldn't:

   config cfg;

   request req;
   req.push("PING", "hello");
   req.push("set", "mykey");
   req.push("get", "mykey");

   boost::redis::generic_response resp;

   asio::io_context ioc;
   connection conn{ioc};

   conn.async_run(cfg, asio::detached);

   conn.async_exec(req, resp, [&](auto, auto) {
      std::cout << "on async_exec" << std::endl;
      conn.cancel();
   });

   ioc.run();

The server will respond with, at least, with nodes like the following: [success, error, success].

This causes the adapter to behave incorrectly in these lines. The error node will emplace an error response in the result, and the next success node will invoke result::value(), throwing an exception.

I don't think this is super urgent but should be kept track of. If I have the time to refactor adapters at some point, I'll fix it.