Connection stuck in bad state after a Redis Error about redis-dart HOT 5 CLOSED

The future chaining that's going on with _future I don't believe will work as expected since when the Future is completed with an error the successor will never be called.

That is good point.

I believe that one possible fix is to wrap return future. We need to keep _future in connection.dart, allays without error and we yield error in future that gets to user.

from redis-dart.

I don't really understand what purpose _future serves but what you're suggesting sounds good to me.

from redis-dart.

_future serves so that we can stack multiple request over same socket and then make repose, to appropriate caller when response is received.
It makes high performance example to work.

I made some modifications. @rajmaniar , can you run some test on your side and report if that improves this issue.

from redis-dart.

The changes seem to work well, thanks!

from redis-dart.

fix released with v2.1.0

from redis-dart.