- Issue created by @davisben
- last update
9 months ago 3 pass, 2 fail - @davisben opened merge request.
- Status changed to Needs review
9 months ago 6:33pm 10 October 2023 - last update
9 months ago 11 pass - Status changed to Needs work
8 months ago 4:47pm 21 October 2023 - 🇷🇺Russia jureth Omsk
1. Why there's a check for ScheduledCronServiceInterface in getLastExecutionTime() ? As I understand the last time value is stored for every handler.
2. Technically, 0 is valid unix timestamp, so I'm not sure why getLastExecutionTime() shouldn't return null in case the value is missing. - last update
8 months ago 11 pass - last update
8 months ago 11 pass - Status changed to Needs review
8 months ago 4:31pm 27 October 2023 - 🇺🇸United States davisben NH
I addressed the concerns in #4, and rebased against 2.0.x.
- last update
8 months ago 11 pass - 🇺🇦Ukraine vasyl.kletsko
vasyl.kletsko → made their first commit to this issue’s fork.
-
vasyl.kletsko →
committed d36d717e on 2.0.x authored by
davisben →
Issue #3393041 by davisben, jureth: Store last execution time
-
vasyl.kletsko →
committed d36d717e on 2.0.x authored by
davisben →
- Status changed to Fixed
8 months ago 8:41am 15 November 2023 Automatically closed - issue fixed for 2 weeks with no activity.