build plan action support

alok760 commented 5 years ago

Fixes #521

Checklist

[x] I have read the Contribution & Best practices Guide and my PR follows them.
[x] My branch is up-to-date with the Upstream master branch.
[ ] The unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)
[ ] All the functions created/modified in this PR contain relevant docstrings.

Test Passing

[ ] The SUSI Server must be building on the pi on bootup
[ ] The hotword detection should have a decent accuracy
[ ] SUSI Linux shouldn't crash when switching from online to offline and vice versa (failing as of now)
[ ] SUSI Linux should be able to boot offline when no internet connection available (failing)

Short description of what this resolves:

Implement an action scheduler which schedules planned actions [wip]

alok760 commented 5 years ago

Still working on this The plan is as follow -

if the reply in busy state contains "plan_delay"
Add the action in that reply to the scheduler.
the scheduler then forwards the action to the busy state after the delay.

alok760 commented 5 years ago

@norbusan please review

norbusan commented 5 years ago

What happens if a planned action is triggered right when the speaker is in the busy state, or recognizing state?

alok760 commented 5 years ago

@norbusan The planned action interrupts the current action and gets executed. So if some other action is being executed in the busy state, it'll stop executing and the planned action will execute. This is not the ideal way for its working. but is ok for now, maybe in future, we can implement a priority queue for the busy state? what do you suggest?

norbusan commented 5 years ago

Merged, thanks

fossasia / susi_linux