generated from TBD54566975/tbd-project-template
-
Notifications
You must be signed in to change notification settings - Fork 8
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
Refactor how the internal scheduled tasks set their timeouts #1381
Labels
good first issue
Good for newcomers
Comments
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently each scheduled task returns a duration which determines when the task will run next. This is flexible, but in practice we never use this, always returning a single value. It also prevents us from easily having separate schedules for production and development, and a production schedule is rarely convenient for development, where we favour responsiveness.
We should remove the ability of tasks to return their own schedule, and instead specify the duration when they're scheduled.
The text was updated successfully, but these errors were encountered: