Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hivemind client (or master) can't handle ask_yesno or get_response() methods #39

Open
JoergZ2 opened this issue Nov 12, 2023 · 0 comments

Comments

@JoergZ2
Copy link

JoergZ2 commented Nov 12, 2023

There may be a connection to post #24 by Goldyfruit: As soon as the ask_yesno() or get_response() methods of Mycroft/OVOS are used in an intent, the HiveMind master can obviously no longer assign the subsequent communication to the skill. The query is still sent to the client, but the subsequent response comes to nothing. At the same time, the listener on the Hivemind master enters an endless loop. It cannot be interrupted by a "Hey Mycroft, stop".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant