Open guyco-redis opened 1 year ago
Hi,
Would you have a use case that generates that situation, in order to prepare a unit test?
According to the specification, all requests except notifications must return a response object.
As a result, it would be more helpful to raise a TypeError
exception with a message indicating that the server returned an invalid response
.
What is your opinion on the matter?
Note: in the master branch of this project, the issue would be on line 632
I have made an issue59 branch with an explicit error. Could you try if it fits your needs?
Hi @tcalmant , unfortunately I don't have a use case that generates this bug, I only saw this traceback through production logs.
Looking through _run_request
which calls self.__transport.request
, this might result by an error like errno.ECONNRESET
, errno.ECONNABORTED
or errno.EPIPE
(which won't raise an exception)?
I think raising an informative TypeError
should be good in this case
Got the following traceback:
from what I could see ServerProxy._request performs self._run_request(request), which can return None, in which case check_for_errors returns the same None, and that is accessed.