Closed kmike closed 13 years ago
I think it's fixed here: branch reconnect . Can you confirm for your case?
Hi, thanks for working on this! I can confirm that reconnections works in my case now.
The recent changes seems to broke the assumption that brukva.client.Client.listen callbacks will receive brukva.client.Message instance as a first parameter (sometimes None is received and it causes AttributeErrors in my code). That's easy to fix on my side though. Is this change intended?
Yes, I can't reproduce AttributeErrors with the latest version.
I think it stops working after this change: https://github.com/evilkost/brukva/commit/6f5514c1782fa7d8411bf3b3b330e40f4f725eec#L1R321
_sudden_disconnect is raising exception now but on_reconnect is usually called after _sudden_disconnect. Exception pops up and prevents reconnection. This is quite easy to reproduce if redis is executed with 'timeout 1' option.
The traceback (not so useful though):