Bug ID: 397332
Summary: No-step scheduler job does a meridian flip and stucks
Target Milestone: ---
Created attachment 114389
Session log - check the last activities to see the problem
While looking for an issue with slewing proceeding while not required, I
created a scheduler job with a sequence that by chance went near the meridian,
and caused a meridian flip.
Because the scheduler job is not requiring tracking, the capture module should
not request a meridian flip. We could add a warning for this when building the
However, when the Capture module executed the flip, the mount obliged but the
flip timed out. The Capture module retried, but no timeout was configured and
as the mount did not reply or something else went wrong that didn't gave the
relevant notification, the Capture module hung there and the whole
Scheduler+Capture got stuck.
You are receiving this mail because:
You are watching all bug changes.