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
{{ message }}
This repository has been archived by the owner on Apr 14, 2024. It is now read-only.
A little bit of research reveals that currently when the client receives a socket error - QAbstractSocket::RemoteHostClosedError, the client does not attempt a reconnect.
This was added to handle cases where version incompatibility checks fail where we do not want to reconnect.
Also, it seems this same error is received irrespective of how drone exits - intentionally, gracefully or crashes out. This makes it impossible to distinguish between the cases on the client side, unless we add some other mechanism to detect the manner of drone exit.
pstavirs
changed the title
Ostinato does not automatically connect to Drone
Ostinato does not automatically re-connect to Drone
Dec 27, 2020
If Drone is killed by pressing
Ctrl-C
, Ostinato does not try to reconnect.This might be expected behaviour - the auto-reconnect is possibly only for unexpected socket closures e.g. drone crashing. Need to check.
The text was updated successfully, but these errors were encountered: