Hang when TCP connection is interrupted

[clach04]

Hang when TCP connection is interrupted

[clach04]

@nijave have you tried tried socket.setdefaulttimeout()? Its not something I've seen with my hardware but I can see how this could happen.

[nijave]

Yeah, that's what I'm using right now

…

On Jan 18, 2018 12:09 AM, "clach04" ***@***.***> wrote: @nijave <https://github.com/nijave> have you tried tried socket.setdefaulttimeout()? Its not something I've seen with my hardware but I can see how this could happen. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#11 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAXd2uv6hIB2cIB9ICL9mDp_2KcUCujJks5tLtH5gaJpZM4RiMfY> .

[clach04]

Cool, if you can make a PR for this that would be awesome. In terms of reporting back to the client, I'm thinking we have something like:

class BaseException(Exception):
    '''Base python-tuya exception'''
    def __repr__(self):
        return repr(self.__dict__)

    def __str__(self):
        return repr(self.__dict__)

class CommsError(BaseException):
    """Communication Error"""
    pass

raise CommsError('timed out on send %r' % realexception.info....)

That way clients can check one thing, the probably don't care about the details (other than for potential debug logging). If that assumption is incorrect we can expand the exceptions. We need to normalize across operating systems (and Python versions), hence suggesting the wrapper. Be interested to get your take on this,