Change Details

Create a scheduler job using the Simulator, with Tracking enabled, to give the tester time to kill the Simulator server. Start the Scheduler, and when it connects and starts to slew, use a terminal to find the PID of the INDI server ("ps -aef | grep indiserver") and kill it ("kill <pid>"). Ekos will immediately register the disconnection, but unfortunately will not tell the Scheduler about it. Without the fix, the Scheduler is hung waiting for the slew to finish and must be stopped manually. With the fix, the Scheduler notices the DBus communication error, aborts the running job and attempts to restart Ekos and reconnect to INDI. Several test runs are needed to kill the Simulator during different stages of the job execution.

Create a scheduler job using the Simulator, with Tracking enabled, to give the tester time to kill the Simulator server. Example of test session: Start the Scheduler, and when it connects and starts to slew, use a terminal to find the PID of the INDI server ("ps -aef | grep indiserver") and kill it ("kill <pid>"). Ekos will immediately register the disconnection, but unfortunately will not tell the Scheduler about it. Without the fix, the Scheduler is hung waiting for the slew to finish and must be stopped manually. With the fix, the Scheduler notices the DBus communication error, aborts the running job and attempts to restart Ekos and reconnect to INDI. Several test runs are needed to kill the Simulator during different stages of the job execution. Testing systematically can be done with a parallel command such as the following ``` $ while true ; do sleep 1 ; if ps -aef | grep indiserver | grep -v grep ; then sleep <delay> ; killall indiserver ; fi ; done ``` In which <delay> is the delay to wait until the indiserver is killed. Tested OK with various delays, killing indiserver while slewing, focusing, guiding, etc. Raised a crash issue when killing a local indiserver while the INDI interface is talking through a pipe as https://bugs.kde.org/show_bug.cgi?id=397774

Create a scheduler job using the Simulator, with Tracking enabled, to give the tester time to kill the Simulator server. Example of test session: Start the Scheduler, and when it connects and starts to slew, use a terminal to find the PID of the INDI server ("ps -aef | grep indiserver") and kill it ("kill <pid>"). Ekos will immediately register the disconnection, but unfortunately will not tell the Scheduler about it. Without the fix, the Scheduler is hung waiting for the slew to finish and must be stopped manually. With the fix, the Scheduler notices the DBus communication error, aborts the running job and attempts to restart Ekos and reconnect to INDI. Several test runs are needed to kill the Simulator during different stages of the job execution. Testing systematically can be done with a parallel command such as the following ``` $ while true ; do sleep 1 ; if ps -aef | grep indiserver | grep -v grep ; then sleep <delay> ; killall indiserver ; fi ; done ``` In which <delay> is the delay to wait until the indiserver is killed. Tested OK with various delays, killing indiserver while slewing, focusing, guiding, etc. Raised a crash issue when killing a local indiserver while the INDI interface is talking through a pipe as https://bugs.kde.org/show_bug.cgi?id=397774