You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Steps to reproduce:
List the minimal actions needed to reproduce the behavior.
Create task with cron at 15:00 (system time) -> for example: option task = {name: "CalculosT1", cron: "0 15 * * *", offset: 15m}
Expected behavior:
This task should be executed EVERY TIME at 15:00 (system time), in my case 14:00 UTC
Actual behavior:
First time after save or after reload docker container, the task runs 1 hour after, at 16 (system time)/ 15:00 UTC, it seems like dont get the cron correctly. Then, the other times it runs at 15:00 (system time)
Environment info:
System info: Linux 4.19.104-microsoft-standard x86_64
@wbaker85 and I are now both seeing this in this test when running locally on our Macs. The problem doesn't reproduce in CI.
EDIT: Might have spoken too soon. We do see an off-by-one failure but it's not on the 1st task run; it's when the task's schedule crosses over a daylight-savings-time boundary.
Steps to reproduce:
List the minimal actions needed to reproduce the behavior.
Expected behavior:
This task should be executed EVERY TIME at 15:00 (system time), in my case 14:00 UTC
Actual behavior:
First time after save or after reload docker container, the task runs 1 hour after, at 16 (system time)/ 15:00 UTC, it seems like dont get the cron correctly. Then, the other times it runs at 15:00 (system time)
Environment info:
Config:
Logs:
Performance:
The text was updated successfully, but these errors were encountered: