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
The documentation of the MMQTTException does not give any advice as to what to do if the exception is raised. Usually, the safest thing would be to reconnect() on the exception, notably because as indicated on #175 (comment) the message data could be partially read and lost when the exception is raised which would result in garbage on the next read.
There are two choices:
easy: augment the MMQTTException docstring
more difficult: to allow for the graceful handling of the read timeout, the buffer should be kept around so that message reassembly can be performed
The text was updated successfully, but these errors were encountered:
The common use case of the library is as follows (adapted from #163 (comment)):
The documentation of the
MMQTTException
does not give any advice as to what to do if the exception is raised. Usually, the safest thing would be toreconnect()
on the exception, notably because as indicated on #175 (comment) the message data could be partially read and lost when the exception is raised which would result in garbage on the next read.There are two choices:
MMQTTException
docstringThe text was updated successfully, but these errors were encountered: