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
Not only is later deprecated, but since we continuously run the tasks server regardless, we really have no need for anything other than plain setInterval. We might also want to consider running a proper job scheduler that runs whole scripts as-needed instead (perhaps Bree).
The text was updated successfully, but these errors were encountered:
My rationale was that setInterval might not be exactly what we want. Similar to how setTimeout is not precise, my understanding is that libraries like later make sure that our tasks run on-time and that a slight error doesn't compound into something bigger.
Understandable (TIL it's not that precise!), although on the timeframes that we're working with, I'm not sure it really matters, plus it's not really that important that our tasks run exactly at 12:00:00, 12:05:00, 12:10:00, etc.
Not only is
later
deprecated, but since we continuously run the tasks server regardless, we really have no need for anything other than plainsetInterval
. We might also want to consider running a proper job scheduler that runs whole scripts as-needed instead (perhaps Bree).The text was updated successfully, but these errors were encountered: