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
I have checked that my issue does not already have a solution in the FAQ
I have searched the existing issues and didn't find my bug already reported there
I have checked that my bug is still present in the latest release
Version
4.0.0a5
What happened?
This issue was reported in #807 for SQLAlchemyDataStore and also mentioend here, but seems not fixed yet for in-memory data store. When a paused schedule created with timezone reaches its trigger time, the next fire time is not correctly updated, resulting in infinite rapid retrying of the scheduler.
Then, upon running this code, the following output can be observed:
Using selector: KqueueSelector
Added new schedule (task='__main__:hello_world', trigger=CronTrigger(year='*', month='*', day='*', week='*', day_of_week='*', hour='*', minute='*', second='*', start_time='2024-10-15T16:25:22.965474-04:00', timezone='America/New_York')); next run time at 2024-10-15 16:25:23-04:00
Scheduler started
Sleeping 0.028 seconds until the next fire time (2024-10-15 16:25:23-04:00)
Sleeping -0.001 seconds until the next fire time (2024-10-15 16:25:23-04:00)
Sleeping -0.001 seconds until the next fire time (2024-10-15 16:25:23-04:00)
Sleeping -0.001 seconds until the next fire time (2024-10-15 16:25:23-04:00)
Sleeping -0.001 seconds until the next fire time (2024-10-15 16:25:23-04:00)
Sleeping -0.001 seconds until the next fire time (2024-10-15 16:25:23-04:00)
Sleeping -0.001 seconds until the next fire time (2024-10-15 16:25:23-04:00)
Sleeping -0.002 seconds until the next fire time (2024-10-15 16:25:23-04:00)
Sleeping -0.002 seconds until the next fire time (2024-10-15 16:25:23-04:00)
Sleeping -0.002 seconds until the next fire time (2024-10-15 16:25:23-04:00)
Sleeping -0.002 seconds until the next fire time (2024-10-15 16:25:23-04:00)
...
The text was updated successfully, but these errors were encountered:
Things to check first
I have checked that my issue does not already have a solution in the FAQ
I have searched the existing issues and didn't find my bug already reported there
I have checked that my bug is still present in the latest release
Version
4.0.0a5
What happened?
This issue was reported in #807 for
SQLAlchemyDataStore
and also mentioend here, but seems not fixed yet for in-memory data store. When a paused schedule created with timezone reaches its trigger time, the next fire time is not correctly updated, resulting in infinite rapid retrying of the scheduler.How can we reproduce the bug?
The following code demonstrates the problem:
Then, upon running this code, the following output can be observed:
The text was updated successfully, but these errors were encountered: