Open guiguem opened 7 years ago
From @laroque on September 22, 2015 17:50
My suspicion is that this must be coming from a latency issue or something, I'm unable to reproduce locally so I'll leave unassigned and as low_priority. If someone wants to take a look at this, a suggestion follows.
A try/catch in service around like 360 could catch on socket.timeout and attempt a reconnect()
and if successful re-call run().
It is worth making sure that if the network is down, the program should actually crash rather than continuing to try and reconnect forever.
From @nsoblath on September 22, 2015 19:35
I think catching the timeout and quitting would be fine. But trying to reconnect once would be added convenience for situations where the network issue is transient.
Mainly I figure that catching the exception and quitting in a nicer way would be good.
From @nsoblath on September 21, 2015 18:18
After some period of inactivity, message_monitor crashes with an unhandled
socket.timeout
exception.I'm not sure what exactly causes this, because I've seen it happen after different amounts of time.
Here's the traceback:
Copied from original issue: project8/dripline#137