How do I resolve this UserWarning?

Rasa Open Source
1

Hi all,

I am getting the following warning. It lists all of my responses.

UserWarning: The following duplicated responses have been found across multiple domain files: utter_mood_great, utter_mood_unhappy, utter_affirm, utter_bot_challenge, utter_deny, utter_did_that_help, utter_goodbye, utter_greet, utter_help

I split up my data so each of the same intents, responses, stories for that intent, etc, is in it’s own file. So I have a file for mood_great that contains its intents, responses, etc. I assume this is the problem, but I do not have the responses duplicated in any file and the documentation makes me believe this should be fine. This method of organization makes the most sense to allow my team to contribute. Each response is only defined once.

2

Can you share your repo.

3

Hi. Thanks for the response. I just used rasa init and then moved contents of files and wrote a few of my own. Example:

$ rasa init
...
$ tree
.
├── actions
│   ├── actions.py
│   ├── __init__.py
│   └── __pycache__
│       ├── actions.cpython-310.pyc
│       └── __init__.cpython-310.pyc
├── config.yml
├── credentials.yml
├── data
│   ├── nlu.yml
│   ├── rules.yml
│   └── stories.yml
├── domain.yml
├── endpoints.yml
└── tests
    └── test_stories.yml

And here’s mine:

$ tree
.
├── actions # untouched
│   ├── actions.py
│   ├── __init__.py
│   └── __pycache__
│       ├── actions.cpython-310.pyc
│       └── __init__.cpython-310.pyc
├── config.yml # untouched
├── credentials.yml # untouched
├── data
│   ├── basic
│   │   ├── affirm.yml
│   │   ├── bot_challenge.yml
│   │   ├── deny.yml
│   │   ├── goodbye.yml
│   │   ├── greet.yml
│   │   ├── help.yml
│   │   ├── mood_great.yml
│   │   ├── mood_unhappy.yml
│   │   ├── out_of_scope.yml
│   │   └── please_rephrase.yml
│   ├── domain.yml
├── endpoints.yml # untouched
├── rules
│   └── rules.yml
└── tests
    └── test_stories.yml # untouched

And in each of the basic files, I just put each section that corresponds to that intent.

$ cat data/basic/affirm.yml 
version: "3.1"

intents:
  - affirm

nlu:
- intent: affirm
  examples: |
    - yes
    - y
    - indeed
    - of course
    - that sounds good
    - correct

responses:
  utter_affirm:
  - text: "Thanks for confirming."

stories:
- story: affirm 1
  steps:
  - intent: affirm
  - action: utter_affirm

And another:

$ cat data/basic/greet.yml 
version: "3.1"

intents:
  - greet

nlu:
- intent: greet
  examples: |
    - hey
    - hello
    - hi
    - hello there
    - good morning
    - good evening
    - moin
    - hey there
    - let's go
    - hey dude
    - goodmorning
    - goodevening
    - good afternoon

responses:  
  utter_greet:
  - text: "Hi. What can I help you with?"

stories:
- story: greet 1
  steps:
  - intent: greet
  - action: utter_greet

Edit: was looking at the wrong branch of the repo.

4

Responses have to be in the domain file. Discussed here. I suspect you have them in both your domain and your training data file based on the error message.

5

Ah, that makes sense then. I misunderstood and thought each of the other files were also considered “domain” files. Thanks for the clarification. I’ll fix that and try again. Thanks!

6

Okay, all responses are now in responses.yml and I’m still getting the error.

7

Check out the rasa train cli options here. Responses are in the domain file and you can configure the file or directory with the --domain option.

8

I’ve been trying that as well. Here are the commands in my train script:

export SQLALCHEMY_SILENCE_UBER_WARNING=1
rasa train --quiet --force --config config.yml \
    --domain data \
    --data data
9

If you put your bot in a git repo, I’ll take a look.

10

In general, you can often ignore various ‘warnings’. If they halted operation, or corrupted results, they’d appear as more serious errors or exceptions-that-must-be-handled for execution to proceed. Specifically here, both warnings are actually about ‘deprecation’ of some method. That typically means a method’s use is discouraged in favor of some newer, more-recommended approach – but still works for now (and possibly for quite a while longer). official dunkinrunsonyou

1 Like
11

Thanks. I was hoping there was something I could do so the warning would disappear, but it seems I’m stuck with it. Thanks all.

12

Thanks for the answers, i was looking for same. .