-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
When adding first user message Rasa is incorrectly pushing two action_listen
events to tracker
#5068
Comments
action_listen
event to trackeraction_listen
events to tracker
There is also another bug connected with this one, that Rasa is falling into infinite loop of ActionDefaultFallback predictions. In Rasa code there is safety limit of action execution and predictions, but in our bot we are manualy calling endpoints for adding message, predicting action and executing predicted action and we have to implement check, that ActionDefaultFallback is not predicted two or more times in a row. |
@tdzienniak Thanks for raising this issue. Did you used |
@tabergma I used Rasa API. |
@tdzienniak I have some trouble reproducing your error. Can you tell me the exact steps you did? I started rasa with |
@tabergma hi, I have more details about this bug. It is also present in Rasa 1.7.0. I have created repository that can be used to reproduce this bug: https://github.com/tdzienniak/rasa-bug-with-mongo-tracker-store . |
I was able to reproduce this, on To reproduce:
My tracker_store:
type: sql
dialect: sqlite
db: tracker.db |
cc @ricwo this is what I mentioned in the |
@tdzienniak so the default trackerstores(InMemory) resulted in this bug? which tracker stores is better to avoid this bug? |
fixed with Rasa Open Source 1.7.4 |
@wochinge This also happens in 2.3.4 when setting |
please! |
Rasa version:
1.6.1
Rasa SDK version (if used & relevant):
Rasa X version (if used & relevant):
Python version:
3.6.9
Operating system (windows, osx, ...):
Ubuntu 19.10
Issue:
When adding first user message Rasa is incorrectly pushing two
action_listen
event to tracker, which results in predicting ActionDefaultFallback instead of proper action defined in conversation. Error occurs when using tracker store different than InMemoryTrackerStore.Full tracker of that conversation:
The text was updated successfully, but these errors were encountered: