search

botpress / v12

Botpress OSS – v12
https://v12.botpress.com
GNU Affero General Public License v3.0
68 stars 83 forks source link

NLU not populating until save #436

Closed rschuetzler closed 5 years ago

rschuetzler commented 5 years ago

I'm running the bot out of docker with volumes for the app directory and node_modules. When I first start up the bot, I have no content in the NLU section. The intents are there, but the training data (utterances) are not. If I create a new utterance under an intent, all data for the other intents is loaded, but the one I edited is wiped out and replaced with the one new utterance I added.

How can I get the NLU data to show up without having to wipe out an intent?

Make sure these checkboxes are checked before raising an issue, thank you!

Please also fill in these fields:

Botpress version: 10.40.0

Channels: Webchat

epaminond commented 5 years ago

@rschuetzler , does the same happen if you run your bot as a regular node-app (outside docker-container)?

rschuetzler commented 5 years ago

@epaminond Seems to work fine when run locally. It fixes another issue, too, where adding entities didn't work correctly. I would tag entities, but it wouldn't recognize it as a change, so I couldn't save until I added a new utterance. Something's wonky inside Docker. Any idea what it is?

epaminond commented 5 years ago

Entities and utterances get saved in plain files if ghost-manager isn't enabled. So I believe an issue is in your Docker setup preventing updating local files (or silently resetting changes).

Closing this since it doesn't look like an issue is in botpress itself.

rschuetzler commented 5 years ago

The files are getting created, because I can see the changes in the Docker volume. It's just that for some reason botpress isn't reading the files when it starts up.

epaminond commented 5 years ago

As far as I can see, botpress uses regular readFile function and there's not much that could go wrong about it's usage within the code. So I still think an issue isn't in botpress itself but maybe in access-rights or some other administrative setup.