D22446: Adding error handling strategy control to Scheduler

[Wolfgang Reissenberger]

wreissenberger added a comment.


  OK, understood. But why did it happen that no frame has been captured? Was it due to the case that as soon as it would have been there turn to be started, they already hit their altitude or twilight limit, right?
  
  The point is, if we set them to aborted and the user selects "restart immediately", it will endlessly loop. That's why I suggest setting them to idle as long as they a) have not been completed AND b) one of their constraints fails.
  
  If we follow this logic, we define completed as having captured the defined number of frames. All other constraints only talk about whether a job may be executed at a certain point of time.
  
  Does that make sense?

REPOSITORY
  R321 KStars

REVISION DETAIL
  https://phabricator.kde.org/D22446

To: wreissenberger, mutlaqja, TallFurryMan
Cc: kde-edu, narvaez, apol
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-edu/attachments/20190918/7d2d3772/attachment.html>