Bug
Chore stalled on time change
Issue description
This happens on a regular basis in fall. Unfortunately it is quite complicated to get this right. One issue is that the decision whether or not to execute a job does not handle the time change, since the timestamp for the job file does not include that information. One alternative could be to switch everything to UTC which has no time lapses.
Developer comments
There seems to be a general problem involved in particular in conjunction with chores. Is the chore interval given in real or calendar time? In most cases calendar time, since otherwise something that runs always on Sunday at 7 in summer time will shift 1 hour in winter time. On the other hand if you have a a job that is run every hour, it will be repeated or skipped on a time lapse. Hell might break loose. Tricky stuff.
The interval is added – as is and thus by default – in calendar time, not real time. This means a chore that runs daily at 8:00, will do so independently of time lapses. It would make sense to implement [11421, the alternative] as well, e.g. imagine a check that has to be repeated every hour (exactly once and only once) even during the strange morning hours of DST switches in spring and fall.
|
Work sessions
Start |
2022-11-06T04:38:44
|
End |
2022-11-06T06:56:45
|
Participant |
Robert Cerny
|
|
We are sorry
This page cannot be displayed in your browser. Use Firefox, Opera, Safari, or Chrome instead.