Serviceless scheduled tasks #44

Closed
opened 2019-04-09 23:44:07 +00:00 by jamie · 13 comments
jamie commented 2019-04-09 23:44:07 +00:00 (Migrated from git.hazaar.io)

Currently there is two ways to schedule tasks. One is to schedule from the application by calling a delayed execution function. The other is using a service. The problem is, using a service leaves a process running the whole time and delayed execution uses a closure. I need a way of scheduling a task to run and starting a new process without using delayed execution.

  • Schedule a task using a static class method including namespace support
  • Schedule a task from the main warlock configuration file
Currently there is two ways to schedule tasks. One is to schedule from the application by calling a delayed execution function. The other is using a service. The problem is, using a service leaves a process running the whole time and delayed execution uses a closure. I need a way of scheduling a task to run and starting a new process without using delayed execution. * [x] Schedule a task using a static class method including namespace support * [x] Schedule a task from the main warlock configuration file
jamie commented 2019-04-09 23:44:23 +00:00 (Migrated from git.hazaar.io)

assigned to @jamie

assigned to @jamie
jamie commented 2019-04-10 11:08:42 +00:00 (Migrated from git.hazaar.io)

added 1m 6s of time spent

added 1m 6s of time spent
jamie commented 2019-04-11 05:34:47 +00:00 (Migrated from git.hazaar.io)

So the thought here is firstly, instead of having to supply a closure to commands like schedule and delay on a Warlock control object, we can somehow pass a class method or function that is executed within the application context.

So the thought here is firstly, instead of having to supply a closure to commands like `schedule` and `delay` on a Warlock control object, we can somehow pass a class method or function that is executed within the application context.
jamie commented 2019-04-11 05:50:26 +00:00 (Migrated from git.hazaar.io)

marked this issue as related to #45

marked this issue as related to #45
jamie commented 2019-04-12 01:40:37 +00:00 (Migrated from git.hazaar.io)

created merge request !17 to address this issue

created merge request !17 to address this issue
jamie commented 2019-04-12 01:40:38 +00:00 (Migrated from git.hazaar.io)

mentioned in merge request !17

mentioned in merge request !17
jamie commented 2019-04-13 05:45:53 +00:00 (Migrated from git.hazaar.io)

changed the description

changed the description
jamie commented 2019-04-13 05:46:38 +00:00 (Migrated from git.hazaar.io)

changed the description

changed the description
jamie commented 2019-04-13 05:46:47 +00:00 (Migrated from git.hazaar.io)

marked the checklist item Schedule a task using a static class method including namespace support as completed

marked the checklist item **Schedule a task using a static class method including namespace support** as completed
jamie commented 2019-04-13 05:46:51 +00:00 (Migrated from git.hazaar.io)

marked the checklist item Schedule a task from the main warlock configuration file as completed

marked the checklist item **Schedule a task from the main warlock configuration file** as completed
jamie commented 2019-04-13 06:00:06 +00:00 (Migrated from git.hazaar.io)

changed milestone to %2

changed milestone to %2
jamie commented 2019-04-13 06:28:36 +00:00 (Migrated from git.hazaar.io)

mentioned in commit 526b12362a

mentioned in commit 526b12362a34cbc566315b572c16664d95c60133
jamie commented 2019-04-13 06:28:37 +00:00 (Migrated from git.hazaar.io)

closed via merge request !17

closed via merge request !17
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: hazaar/hazaar-warlock#44
No description provided.