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
On most platforms, BlockingIOError is raised with an errno.EWOULDBLOCK error number. But Jypthon(on Windows) uses a different error to indicate that the socket would block which is errno.EAGAIN error number. NONBLOCKING_EXCEPTIONS tuple only have errno.EWOULDBLOCK on the whitelist.
But the error is errno.EAGAIN , so the if condition is false and then raise ConnectionError
While developing, I face this error. After searching, I found https://bytemeta.vip/repo/andymccurdy/redis-py/issues/1387?page=1 to fix it.
Sumary
On most platforms,
BlockingIOError
is raised with anerrno.EWOULDBLOCK
error number. But Jypthon(on Windows) uses a different error to indicate that the socket would block which iserrno.EAGAIN
error number.NONBLOCKING_EXCEPTIONS
tuple only haveerrno.EWOULDBLOCK
on the whitelist.But the error is
errno.EAGAIN
, so the if condition is false and then raiseConnectionError
Solution
Add the
errno.EAGAIN
to the whitelist only once.The text was updated successfully, but these errors were encountered: