-
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
rasa validate KeyError during story conflict testing #7603
Comments
I am also facing similar issue both on 2.2.1 and 2.2.2
|
Downgrade rasa to 2.1.3 and retrain the model solves the problem for me.
|
Thanks Nriver. 2.1.3 is indeed a (temporary) solution but there are still issues, see this post from Rasa blog. |
This bug was introduced in this commit 954e473#diff-b9a6da0b97982d86712af2c20891570d9fa8d662a4d4fbf0e018b085eaaaf8e9 See |
Renamed issue since this issue is not specific to retrieval intents. Duplicated this issue with story: - story: time_from
steps:
- intent: time_from
- action: action_time_range states: {"prev_action": {"action_name": "action_listen"}, "user": {"intent": "time_from"}} state[USER]: {"intent": "time_from"} |
Rasa version: 2.2.1
Rasa SDK version: 2.2.0
Rasa X version: 0.34.0
Python version: 3.7.9
Operating system: Windows-7-6.1.7601-SP1
Issue: rasa data validate throws error when using retrieval intents - also ResponsesSeclector responses need to be out of
domain.ym
unlike indicated by the online documentation on chitchat and faq can be reproduced with RasaHQ responselectorbotError (including full traceback):
Command or request that led to error:
Content of configuration file (config.yml) (if relevant):
Content of domain file (domain.yml) (if relevant):
Content of nlu file (nlu.yml) (if relevant):
Content of stories file (stories.yml) (if relevant):
Content of rules file (rules.yml) (if relevant):
The text was updated successfully, but these errors were encountered: