On 03/04/2019 10:50 pm, Andrew Stitcher wrote:
On Wed, 2019-04-03 at 22:02 +0100, Gordon Sim wrote:
It looks like the reconnect capability in the python client is broken
on
master. Is this a known issue?
Any chance of some more details or a reproducer?
Just run any of the examples either against a port with no broker, or
kill the broker after client has connected. On 0.26.0 the client will
keep trying to reconnect. On master it exits immediately with a
socket.error.
The current python
bindings *should* work the same (by design) as the previous
implementation.
I think the issue is that the loss of the socket no longer results in a
transport_close event? (or that the socket.error is raised and causes
the loop to exit before processing that event?)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
