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.

Sign up for GitHub

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

Jump to bottom

[BUG] neon-core-skills keeps reporting "mycroft should already have reported ready!" #582

Open
mikejgray opened this issue Nov 22, 2023 · 1 comment
Open

[BUG] neon-core-skills keeps reporting "mycroft should already have reported ready!" #582

mikejgray opened this issue Nov 22, 2023 · 1 comment
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@mikejgray
Copy link
Contributor

Description

When running neon-core-skills as a container, it repeatedly logs that "mycroft should already have reported ready!" Ideally this would not happen in a containerized environment, as you will only get that message once - maybe it should emit a bus message expecting a response that Mycroft is ready instead of constantly waiting for one unprompted?

Steps to Reproduce

Run Neon Diana
Check the neon-core-skills container logs

Relevant Code

No response

Other Notes

No response
@mikejgray mikejgray added the bug Something isn't working label Nov 22, 2023
@NeonDaniel
Copy link
Member

This could be a default config question.. For k8s, we could configure this to only wait for audio; I believe that one is actually necessary for OCP intents to register properly

@NeonDaniel NeonDaniel added the help wanted Extra attention is needed label May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
Community Projects
Status: Other Helpful Tasks
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mikejgray @NeonDaniel