Gracefully handle when intents in stories.yml
or rules.yml
have no value
#8587
Labels
area:rasa-oss 🎡
Anything related to the open source Rasa framework
area:rasa-oss/training-data
Issues focused around Rasa training data (stories, NLU, domain, etc.)
effort:atom-squad/1
Label which is used by the Rasa Atom squad to do internal estimation of task sizes.
tool:sentry
type:bug 🐛
Inconsistencies or issues which will cause an issue or problem for users or implementors.
Sentry Issue: RASA-OPEN-SOURCE-9YN
Stack Trace
Further Information
This error can be reproduced if we have an intent with no value :
in
rules.yml
like shown belowor in
stories.yml
like shown below** Command that led to error**:
Potential Solutions
step.get(KEY_USER_INTENT, "")
has a value and otherwise it raises :InvalidRule
error if the object is a RuleParserInvalidStory
error if the object is a StoryParserFun Fact
_user_intent_from_step
has an argument calledstep
and python debuggerpdb
has a command calledstep
. So if someone wants to debug withpdb
while being inside that function and tries to see what the variablestep
has by giving(Pdb) step
tough luck! It will just move on the next statement. Temporarily renaming the argument works though. :)The text was updated successfully, but these errors were encountered: