-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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 1.6.0 breaks custom components #4995
Comments
Actually... looks like this is the problem. The default value for use_cls_token in tokenizer.py was changed from False to True. |
@samscudder thanks a lot for the report. @tabergma in the previous implementation, we actually checked if the (e.g. why not go with something like |
The default value should be set to |
Shouldn't this be a warning instead of an error then? |
To help anybody else that has this problem while you decide what needs to be done..., the recommended course or action for < 2.0 would be to add |
For custom tokenizer you should add
to your default dict in your custom components. For custom featurizers you should add
to your default dict in your custom components. Will update the docs and print warning instead of the error. |
Rasa version: 1.6.0
Rasa SDK version (if used & relevant): 1.6.0
Python version: 3.6.9 (anaconda)
Operating system (windows, osx, ...): RHEL 7 (CentOS)
Issue: Custom components now fail during training, caused by this:
[https://github.com/RasaHQ/rasa/commit/255b91088a57c45a766af37826845b8c936a0a77]
Documentation doesn't reflect this alteration.
Error (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):
**CustomLemmatization.py file:
The text was updated successfully, but these errors were encountered: