You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit 57f92d9
changes the behaviour if a connection error occures. This happens at our side during sync of slave and master redis servers (takes about 5 to 10secs) and requesting keys (getitem) meanwhile.
Currently we are receiving a ConnectionError object and try to handle this object as a valid result. This finally ends up in a TypeError Exception because we are expecting a string here.
The question here is if that is the expected behaviour and we are doing something wrong.
We are catching a ConnectionError and try to reconnect, but with this change the Error is not raised anymore.
The text was updated successfully, but these errors were encountered:
This commit
57f92d9
changes the behaviour if a connection error occures. This happens at our side during sync of slave and master redis servers (takes about 5 to 10secs) and requesting keys (getitem) meanwhile.
Currently we are receiving a ConnectionError object and try to handle this object as a valid result. This finally ends up in a TypeError Exception because we are expecting a string here.
The question here is if that is the expected behaviour and we are doing something wrong.
We are catching a ConnectionError and try to reconnect, but with this change the Error is not raised anymore.
The text was updated successfully, but these errors were encountered: