-
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
Remove Policy deprecations and set max_history default to None. #9119
Conversation
rasa/core/policies/ensemble.py
Outdated
from rasa.core.policies.form_policy import FormPolicy | ||
|
||
suited_policies_for_forms = (FormPolicy, RulePolicy) | ||
suited_policies_for_forms = (RulePolicy) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These parenthesis are doing nothing. You would need a comma to make it a tuple, but probably a tuple is not needed now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed the tuple and just now check that there is a rule policy instance in the config to handle forms.
reminder to tackle
|
The CI tests are now passing but our core regression tests are failing. Looking into this some more, I see that the problem is unrelated to this PR. It seems that Unfortunately, the two repos we run core regression tests on (finanicial-demo and helpdesk-assistant) have not had their domain files updated. I have created PRs for each of them to add this field (here and here). Once they have merged core regression tests should work again. Although none of the core policy regression tests include any of the deprecated policies removed in this PR so the core regression tests should not be affected by any of the changes here (in theory, I wanted to run core regression tests now to confirm this which is how I discovered they were broken). We could merge if this PR is blocking other work and the core regression tests will get fixed when those other repos update their domain files? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall looks good but I think we'll need to talk about how we deal with links to removed components, as well as with migration automation code that isn't for the current major version (in this case 3.x).
Co-authored-by: Sam Sucik <s.sucik@rasa.com>
Hey @kedz! 👋 To run model regression tests, comment with the Tips 💡: The model regression test will be run on Tips 💡: Every time when you want to change a configuration you should edit the comment with the previous configuration. You can copy this in your comment and customize:
|
/modeltest include:
- dataset: ["all-core"]
config: ["all-core"] |
The model regression tests have started. It might take a while, please be patient. Used configuration can be found in the comment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, let's deal with the links and then we're good to go I think 🙂
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I love the smell of deleted code in the morning 🥀
@kedz I think so 😉 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
Proposed changes:
FormPolicy
MappingPolicy
FallbackPolicy
TwoStageFallbackPolicy
SklearnPolicy
MemoizationPolicy
.Status (please check what you already did):
black
(please check Readme for instructions)