-
Notifications
You must be signed in to change notification settings - Fork 79
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
npm run sonus error UnhandledPromiseRejectionWarning after a while #22
Comments
this issue is with node-record-lpcm16 it uses execa |
Thanks for the detailed issue! I'll take a look at this over the weekend. The Node.js Child Processes module (child_process) has two functions I'm going to look into creating a custom implementation for this, because it looks like node-record-lpcm16 doesn't meet our needs. |
Hey Evan! Any luck so far? I'm researching workarounds in the meantime... but am not having much luck :( |
This should be fixed with the most recent version of sonus Upgrade and reinstall dependencies and let me know if that works for you. |
Just updated everything and it's working perfectly! Thank you so much!! :D |
Description :
Sonus is in the smart mirror project, in this project I have the error below after let's say 5 to 8 mn of running, the hotword detection works fine and I have no problem with the google speech api.
How to reproduce
Comments
At first I thought it was an issue on the smart-mirror or in my config.js file, but then I ran
"npm run sonus" just to test the audio capture, just wait around 5 to 8 mn and to do nothing and the error occured too.
Configuration
For information, this is my configuration
Ideas
From what I have read around the web, it can be caused by two main things
set the maxBuffer option when using child_process.exec
stdout-buffer-issue-using-node-child-process
a missing catch in a promise call
promise-reject-possibly-unhandled-error
Do you have an idea ?
Laurent
The text was updated successfully, but these errors were encountered: