use_entities is broken when domain is split
See original GitHub issueRasa Open Source version
2.8.12
Rasa SDK version
2.8.2
Rasa X version
No response
Python version
3.8
What operating system are you using?
Linux
What happened?
Create a domain.yml with the following content:
intents:
- greet:
use_entities: [country]
- goodbye:
use_entities: []
- affirm
- deny
- mood_great
- mood_unhappy
- bot_challenge
entities:
- city
- country
Create another domain yaml with the following content:
intents:
- inform:
use_entities: [city]
Reading the merged domain files using Domain.load
shows that the intent inform
is still using the entities city
and country
.
The workaround is to repeat the list of entities in the first domain file in the second domain file i.e.:
intents:
- inform:
use_entities: [city]
entities:
- city
- country
Here is the code to reproduce this behavior.
Command / Request
No response
Relevant log output
No response
Definition of done
- Fix bug in 2.8 and 3.0
- Create integration test to ensure this works as expected
- Fixed merged into 2.8 and 3.0
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:18 (18 by maintainers)
Top Results From Across the Web
Split tunneling based on the domain is not working.
Split tunneling based on the domain is not working. We need to monitor our user's web traffic while they are on roaming.
Read more >What Is The Split Domain Option? - Intermedia
Enabling a split domain allows you to receive your mail in two locations. When you enable the Split Domain option, the Exchange server...
Read more >Active Directory domain split and clone after company demerger
The idea was to migrate all Company-B AD objects from Company-A.com to Company-B.com, then “cut” the network between the two companies forever.
Read more >Fully Qualified Domain Name (FQDN) split tunnel rule(s) is ...
This article provides details about the behavior of Fully Qualified Domain Name (FQDN) split tunneling with a deny rule. Problem or Goal. If...
Read more >New Question on AnyConnect Split Tunnel Setup for O365
Domain names beyond that limit are ignored. A custom attribute cannot exceed 421 characters. If a larger value is entered, ASDM breaks it...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@TyDunn I’ve raised a PR for
2.8.x
and added a unit test. I don’t think we need an integration test as the bug was isolated to a quirk in one of theshared.core.domain
class methods only…@raoulvm this fix has now been released in
2.8.19
: https://pypi.org/project/rasa/2.8.19/