Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Notification#BeginExecuteNotification(): SetNextNotification() correctly #6896
already checks the boundaries here, which is why we can just set next_notification to the delayed value.
@mdetrano can you test whether this fixes your reported problem?
Finally had a chance to build and test with this fix merged in. Looks good. Notifications go out at the correct times when the begin time is not "0". No longer matters if the "next notification" falls after or before the calculated "begin" time. Should be sufficient to fix Issue #5561.