Now that I am back from vacation I wanted to try the scheduler with KStars 2.9.7 for the first time. I started the scheduled job after the planned start time, but the scheduler did not start the job, but went idle with the message sleeping till <start time> which had already passed.
Is this a known issue in the new version?
Skywatcher Newton 200/1000, Sharpstar 60ED, Canon Lenses
Skywatcherr EQ-6 R, AZ-GTI
StellarMate @ Raspberry Pi 3B+
ASI 183 MC Pro
ASI 290 MC guiding cam on APM 60 ImageMaster
Sesto Senso 2 Focuser + Astromechanics Canon Focuser
No, I started it around August 12th around 22:33 and it said sleeping till August 12th 22:28.
Skywatcher Newton 200/1000, Sharpstar 60ED, Canon Lenses
Skywatcherr EQ-6 R, AZ-GTI
StellarMate @ Raspberry Pi 3B+
ASI 183 MC Pro
ASI 290 MC guiding cam on APM 60 ImageMaster
Sesto Senso 2 Focuser + Astromechanics Canon Focuser
No logs this time. I will try to log it next time.
Skywatcher Newton 200/1000, Sharpstar 60ED, Canon Lenses
Skywatcherr EQ-6 R, AZ-GTI
StellarMate @ Raspberry Pi 3B+
ASI 183 MC Pro
ASI 290 MC guiding cam on APM 60 ImageMaster
Sesto Senso 2 Focuser + Astromechanics Canon Focuser
That could be August next year, but I'm not convinced
I spotted a problem with seconds calculation in QDateTime when the result should be negative. And 22:28 to 22:33 is precisely the 5-minute lead time after which a job is aborted. That could very well be an edge case of this feature.
I have a commit for this in my test queue, but for another reason: the logs saying "job is passed by" on fixed-start jobs that are more than one day in the past are indicating the passed time with a 24-hour modulo (day-old job marked passed by 15 minutes). Let's see if I can reproduce and use that fix. Thanks for reporting!