Dispatch Managing Actor #54
Commits on Sep 30, 2024
-
Send STOPPED message when duration is reached
Signed-off-by: Mathias L. Baumann <[email protected]>
-
Fix wrong running behaviors with duration=None
* Dispatch.running() was always returning RUNNING for duration None * Dispatch.next_run_after() was made aware that there is no next run for inf. Duration * Dispatch._until() now raises when used with Dispatch.None * Actor: delay marking a Dispatch as deleted, otherwise checks wrongly detect it as no longer running. Signed-off-by: Mathias L. Baumann <[email protected]>
-
Rewrite internal architecture to be more flexible
The internal scheduling architecture was rewritten: Instead of using one task per dispatch that will start/stop them, we now have a queue of events and a timer that is rescheduled to the earliest next event each time it triggers. Previously we had to do complicated re-scheduling and cancelling of tasks, now we always just update the event in the queue. Signed-off-by: Mathias L. Baumann <[email protected]>
-
A useful actor to help control and manange another actor using dispatches. Signed-off-by: Mathias L. Baumann <[email protected]>
-
DispatchManagingActor: Support starting/stopping of multiple actors
Signed-off-by: Mathias L. Baumann <[email protected]>
-
Fix wrong Dispatch.running() behavior with duration=None
Signed-off-by: Mathias L. Baumann <[email protected]>
-
DispatchActor: Update timer correctly after schedule modifications
Signed-off-by: Mathias L. Baumann <[email protected]>
-
Set dependency to latest dispatch-client
Signed-off-by: Mathias L. Baumann <[email protected]>
-
Update event_loop to explicitly set scope session
As recommended by the deprecation warning Signed-off-by: Mathias L. Baumann <[email protected]>
-
Wrap scheduler to tolerate somehow invalid dispatches
Signed-off-by: Mathias L. Baumann <[email protected]>
-
Add test that notifications are sent at startup
Signed-off-by: Mathias L. Baumann <[email protected]>
