Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
[Scheduler] FixPeriodicalTrigger from argument for stateful run dates#50818
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
[Scheduler] FixPeriodicalTrigger from argument for stateful run dates#50818
Uh oh!
There was an error while loading.Please reload this page.
Conversation
carsonbot commentedJun 29, 2023
Hey! I see that this is your first PR. That is great! Welcome! Symfony has acontribution guide which I suggest you to read. In short:
Review the GitHub status checks of your pull request and try to solve the reported issues. If some tests are failing, try to see if they are failing because of this change. When two Symfony core team members approve this change, it will be merged and you will become an official Symfony contributor! I am going to sit back now and wait for the reviews. Cheers! Carsonbot |
PeriodicalTrigger from argument for stateful run datesed04289 tocb9be9fComparenicolas-grekas commentedJul 5, 2023
Thank you@StanJansen. |
Summary: Unless you provide the
fromargument (with a date in the past), caching will not work for thePeriodicalTrigger.If the
fromargument is not passed to theRecurringMessage::everymethod, it will, fallback tonew \DateTimeImmutable(). If you use a stateful schedule and you restart the consumer (either manually or using a time limit), the cached last-executed date will always be overridden by the moment you restart the scheduler due toif ($this->from > $run) {.