leon: Leon don't want to talk french, angry omelette du fromage
Specs
- Leon version: beta 3
- OS (or browser) version: Windows 10 but Leon on WSL Ubuntu 18
- Node.js version: 11
- Complete “npm run check” output:
---
.: CHECKING :.
➡ /bin/sh -c node --version
✔ v11.15.0
➡ /bin/sh -c npm --version
✔ 6.7.0
➡ /bin/sh -c pipenv --version
✔ pipenv, version 2018.11.26
➡ /bin/sh -c pipenv --where
✔ /home/user/leon-dev/bridges/python
➡ /bin/sh -c pipenv run python --version
✔ Python 3.6.7
➡ /bin/sh -c pipenv run python bridges/python/main.py scripts/assets/query-object.json
✔ {"package": "leon", "module": "randomnumber", "action": "run", "lang": "en", "input": "Give me a random number", "entities": [], "output": {"type": "end", "codes": ["success"], "speech": 8, "options": {}}}
➡ Classifier state
✔ Found and valid
➡ Amazon Polly TTS
❗ Amazon Polly TTS is not yet configured
➡ Google Cloud TTS/STT
❗ Google Cloud TTS/STT is not yet configured
➡ Watson TTS
❗ Watson TTS is not yet configured
➡ Offline TTS
❗ Cannot find bin/flite/flite. You can setup the offline TTS by running: "npm run setup:offline-tts"
➡ Watson STT
❗ Watson STT is not yet configured
➡ Offline STT
❗ Cannot find bin/deepspeech/lm.binary. You can setup the offline STT by running: "npm run setup:offline-stt"
---
.: REPORT :.
➡ Here is the diagnosis about your current setup
✔ Run
✔ Run modules
✔ Reply you by texting
❗ Amazon Polly text-to-speech
❗ Google Cloud text-to-speech
❗ Watson text-to-speech
❗ Offline text-to-speech
❗ Google Cloud speech-to-text
❗ Watson speech-to-text
❗ Offline speech-to-text
✔ Hooray! Leon can run correctly
➡ If you have some yellow warnings, it is all good. It means some entities are not yet configured
Actual Behavior
When i talk whit Leon in french it’s crash
How Do We Reproduce?
Talk french with Leon :p
Extra (like a sample repo to reproduce the issue, etc.)
(node:1042) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'split' of undefined
at Nlu.process (/home/user/leon-dev/server/dist/core/nlu.js:103:45)
at processTicksAndRejections (internal/process/task_queues.js:86:5)
(node:1042) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:1042) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 17 (9 by maintainers)
After digging into some debugging, the issue is fixed quite strangely.
A simple new build (
npm run build
andnpm start
) fixed it. I suppose it was due to a change in the code that was not update or something similar.I’ll close this issue as it is now working.