When disconnecting the client, we have to cancel the uaclient _publish_task.
If we don't, this can prevent reconnection since the task is still running, and the previous task instance could be hanging on a previous request that has never completed (i.e network issue). Yes, there's no timeout on request coming from the publish_loop, so we must ensure the publish_task is always cancelled. Hence, the uaclient.close_session is always called on disconnect.
Showing
Please register or sign in to comment