-
Notifications
You must be signed in to change notification settings - Fork 68
Open
Description
I didn't look into this issue to much, because using threading directly works and bypasses this problem. So this means I am not 100% certain of the following.
It seems that the scheduler expects the tasks do be finite. So if there are some task like the following, then scheduler fails to execute some of them. The problem there is that it does so without error message.
self._sh.scheduler.add('test_1', self._worker, prio=3, cron='init', cycle=None, value=None, offset=None, next=None)
self._sh.scheduler.add('test_2', self._worker, prio=3, cron='init', cycle=None, value=None, offset=None, next=None)
...
def _worker(self):
while self.alive:
passThe scheduler also seems to miss task if the cycle time is to short.
self._sh.scheduler.add('test_1', self._worker, prio=3, cron=None, cycle=1, value=None, offset=None, next=None)
self._sh.scheduler.add('test_2', self._worker, prio=3, cron=None, cycle=1, value=None, offset=None, next=None)
...Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels