Am 10.04.17 um 17:58 schrieb David Osborne:
The order change is changing which callback is timing out first and
backendReply was triggered. It doesn't deal with the timeout properly,
it just immediately starts trying to read from the backend chan.
Thanks for the changes. The exception handling w
This had a knock-on effect meaning the timeout stopped functioning for me.
The order change is changing which callback is timing out first and
backendReply
was triggered. It doesn't deal with the timeout properly, it just
immediately starts trying to read from the backend chan.
So adding timeout
