-
Notifications
You must be signed in to change notification settings - Fork 17
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
ENG-1293: Update rasa-calm-demo
to version 3.10.1
#57
ENG-1293: Update rasa-calm-demo
to version 3.10.1
#57
Conversation
fcd29c0
to
6470a0e
Compare
…ailure, to assist in troubleshooting
Remove `utter_clarification_options_rasa` assertion in the following two failing tests, as now this step won't be reached: 1. e2e_tests_with_assertions/passing/disambiguation/user_sends_short_verb_only_message.yml::user sends short verb only message 2. e2e_tests_with_assertions/passing/negations/users_says_they_dont_want_the_former_option.yml::user says they don't want the former option
…nding test, corrected it now
19eaebb
to
63765a5
Compare
rasa-calm-demo
to version 3.10.1rasa-calm-demo
to version 3.10.1
data/flows/patterns.yml
Outdated
action: utter_clarification_options_rasa | ||
|
||
pattern_clarification_with_human_handoff: |
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.
Is this a new pattern added to the default file in rasa-private? Or should this be overriding pattern handoff?
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.
iiuc this is a new pattern added to rasa-private
recently in #966
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.
This file on main
doesn't contain such pattern, so Rasa will not classify it as a pattern, but as a user defined flow: https://github.com/RasaHQ/rasa-private/blob/main/rasa/dialogue_understanding/patterns/default_flows_for_patterns.yml
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 looked at the PR and the changelog mentions that pattern_human_handoff
can now be linked in other flows, therefore this flow should be overriding that pattern name.
``` | ||
|
||
#### E2E tests with assertions |
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.
Thanks for updating the readme 👍🏻
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.
The changes in the 2 e2e tests with assertions that were previous failing LGTM 👍🏻 I didn't look in depth at other changes, apart from leaving a question a new pattern.
… on recent pattern-clarification changes
Currently CI blocked again due to: https://rasa-hq.slack.com/archives/C36SS4N8M/p1726502977324429 |
Issue seems resolved now and CI pipeline (and all tests therein) passed ✅ https://github.com/RasaHQ/rasa-calm-demo/actions/runs/10886834156 |
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.
We should add a test to check that the link to pattern_human hand off works
… triggered in relevant conditions On these conditions: 1. When `pattern_clarification` is triggered twice 2. Or when login fails during check-portfolio at least 3 times
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.
LGTM
* Add a new folder of updated e2e tests with assertions (#46) * update some e2e_tests to the new assertions format * adapt 2 correction test cases * adapt all cancellations, chitchat, disambiguation * adapt test cases in invalid_path, invalid_user_inputs, negations, potential_bugs * adapt digressions, flow_guards, skip_question * adapt tests for corrections * adapt all happy_path test cases * fix error in running datetime validation in the custom actions * add generative assertion test cases * update gitignore * Add assertions for failing and flaky tests * udate rasa-pro to 3.10.0rc1 * add mlflow optional dependency, add new workflow and new make commands * fix CI deprecation warning, fix failing test case * update threshold to prevent flakiness * update button payload and test case * fix flaky passing e2e test --------- Co-authored-by: Maksim Moiseikin <[email protected]> * Add example stub custom actions (#49) * add some updated existing tests in a separate folder, add a new CI workflow and make command * add chitchat generative assertions test case * update to rasa pro 3.10.0rc2 * set assertion_order_enabled to true in 1 test step * Replace hardcoded currency strings with a regex parsing [ENG-1303] This will fix a TypeError when we get a string like "50 dollars" * update to rc3 * update rasa-pro version (#54) * ENG-1293: Update `rasa-calm-demo` to version 3.10.1 (#57) * link to add_contact in pattern_clarification * link from check_portfolio to pattern_human_handoff * link from pattern_clarification to pattern_human_handoff * do not rephrase utter_human_handoff_not_available * ENG-1293: Added pattern_human_handoff flow * ENG-1293: Running tests with `--e2e-results`, and saving results on failure, to assist in troubleshooting * ENG-1293: Update `rasa-calm-demo` to version 3.10.1 * ENG-1293: Fix 2 failing tests Remove `utter_clarification_options_rasa` assertion in the following two failing tests, as now this step won't be reached: 1. e2e_tests_with_assertions/passing/disambiguation/user_sends_short_verb_only_message.yml::user sends short verb only message 2. e2e_tests_with_assertions/passing/negations/users_says_they_dont_want_the_former_option.yml::user says they don't want the former option * ENG-1293: fix mistake, had removed assertion from a wrong similar sounding test, corrected it now * ENG-1293: fix/update test `user_sends_short_verb_only_message`, based on recent pattern-clarification changes * ENG-1293: properly add `pattern_human_handoff` to default `pattern_clarification` * ENG-1293: Add tests to verify that link to `pattern_human_handoff` is triggered in relevant conditions On these conditions: 1. When `pattern_clarification` is triggered twice 2. Or when login fails during check-portfolio at least 3 times --------- Co-authored-by: Tanja Bunk <[email protected]> --------- Co-authored-by: Anca Lita <[email protected]> Co-authored-by: Maksim Moiseikin <[email protected]> Co-authored-by: Tanja Bunk <[email protected]>
Description
Update rasa calm demo to version 3.10.1. As part of that:
add_contact
inpattern_clarification
#48.a. Updated/fixed effected tests accordingly.
b. Added tests to verify that link to
pattern_human_handoff
is triggered in relevant conditions (when 2 clarifications reached or when 3 auth fails during portfolio-check)--e2e-results
flag and saving test results for unsuccessful CI steps, to ease with local troubleshooting of test failures.Once above changes are merged to
release-3.10
, thenrelease-3.10
can be merged tomain
to update to3.10.1
.Note:
Currently CI pipeline is blocked though due to OpenAI rate-limit issue:Sorted: OpenAI usage budget limit is now updated/increased and this issue is resolved, so CI pipeline was able to proceed and all tests passing now ✅OpenAIException - Error code: 429 - ***'error': ***'message': 'You exceeded your current quota, please check your plan and billing details.
(issue raised in dev-tribe), so currently keeping this PR as Draft.TODOs