Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jobs scheduled to run at midnight, are scheduled for midnight of the preceding day #2145

Open
stevecoh1 opened this issue Nov 1, 2024 · 1 comment
Labels

Comments

@stevecoh1
Copy link

Describe the bug
When a job is scheduled with a date of midnight the next day, it appears on the schedule as midnight the current day. If the user fails to notice this, and starts the schedule, the job executes immediately, rather than at the intended start time. The workaround is to start the job at 00:01 rather than midnight.

To Reproduce
Very simple to reproduce:
Enter a job with a start time of midnight, the following day.
When the job is added to the schedule, it appears as midnight of the current day (i.e. in the past)

Expected behavior
The job should be entered in the schedule as it was entered by the user, i.e. midnight tomorrow.

Screenshots

Desktop (please complete the following information):
Stellarmate Pro, although I reproduced it using the VNC interface, i.e. on the device itself.

Log Files

@stevecoh1 stevecoh1 added the bug label Nov 1, 2024
@stevecoh1
Copy link
Author

screenshots included

  1. User entered tomorrow at midnight but not added to schedule
    Screenshot from 2024-11-01 12-01-56
  2. After user clicked (+) to add to the schedule.
    Screenshot from 2024-11-01 12-02-21

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant