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

Adding sensible error messages when susi crashes #528

Open
sansyrox opened this issue Nov 22, 2019 · 4 comments
Open

Adding sensible error messages when susi crashes #528

sansyrox opened this issue Nov 22, 2019 · 4 comments

Comments

@sansyrox
Copy link
Member

Is your feature request related to a problem? Please describe.

Currently, SUSI only sends out one error message when it crashes.

Describe the solution you'd like

Different error messages depending on the issue.

Additional context

Only changes in the state machine required.

@norbusan
Copy link
Member

When SUSI crashes, you mean the susi_linux process? But when it crashes, how could it give sensible messages? Ok, we could create a state file, clean it up on proper shutdown, and when systemd restarts the susi_linux process and it finds the state file, it could tell the user that susi linux has crashed, but how do you intend to get details?

@sansyrox
Copy link
Member Author

@norbusan , I meant for example when there is an issue with the internet connection or it is a problem with deploying Java server on the Pi . These errors are handled in the error_state file. But only one kind of sound played when it enters the error state.
Instead of that, we should play different sounds for easier debugging.

@norbusan
Copy link
Member

Ok, so you mean for TTS or STT, when the connection timed out.
What about problems communicating with the onboard susi_server, can we detect that, too?

@sansyrox
Copy link
Member Author

@norbusan , yes we handle those too. I think we log the errors somewhere as of now.

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

2 participants