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
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
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