Merge pull request #20 from RasaHQ/update_rasa_version

Update to rasa 3.8.0

.github/workflows/continous-integration.yml

@@ -12,7 +12,7 @@ concurrency:
 
 env:
   DEFAULT_PYTHON_VERSION: '3.9'
-  POETRY_VERSION: 1.4.2
+  POETRY_VERSION: 1.8.2
 
 jobs:
   train-model:
@@ -156,14 +156,22 @@ jobs:
         path: .rasa
         key: rasa-llm-cache
 
-    - name: Run e2e passing tests
+    - name: Run action server
       env:
         OPENAI_API_KEY: ${{secrets.OPENAI_API_KEY}}
         RASA_PRO_LICENSE: ${{secrets.RASA_PRO_LICENSE}}
         RASA_DUCKLING_HTTP_URL: ${{secrets.DUCKLING_URL}}
         RASA_PRO_BETA_INTENTLESS: true
       run: |
         make actions &
+
+    - name: Run e2e passing tests
+      env:
+        OPENAI_API_KEY: ${{secrets.OPENAI_API_KEY}}
+        RASA_PRO_LICENSE: ${{secrets.RASA_PRO_LICENSE}}
+        RASA_DUCKLING_HTTP_URL: ${{secrets.DUCKLING_URL}}
+        RASA_PRO_BETA_INTENTLESS: true
+      run: |
         make test-passing
 
     - name: Run e2e flaky tests
@@ -173,7 +181,6 @@ jobs:
         RASA_DUCKLING_HTTP_URL: ${{secrets.DUCKLING_URL}}
         RASA_PRO_BETA_INTENTLESS: true
       run: |
-        make actions &
         make test-flaky || true
 
     - name: Run e2e failing tests
@@ -183,5 +190,4 @@ jobs:
         RASA_DUCKLING_HTTP_URL: ${{secrets.DUCKLING_URL}}
         RASA_PRO_BETA_INTENTLESS: true
       run: |
-        make actions &
         make test-failing | grep '0 passed'

README.md

@@ -166,7 +166,7 @@ and run end-to-end tests.
 Prerequisites:
 - rasa pro license
 - being authenticated with our artifact registry
-- [poetry](https://python-poetry.org/docs/#installation) (1.4.2), e.g. using 
+- [poetry](https://python-poetry.org/docs/#installation) (1.8.2), e.g. using 
   `poetry self update`
 - python (3.10.12), e.g. using [pyenv](https://github.com/pyenv/pyenv) 
   `pyenv install 3.10.12`
@@ -258,20 +258,26 @@ run rasa test e2e e2e_tests
 
 ------
 
-To run **passing/failing** tests you can use the `make` command:
+To run **passing/failing/flaky** tests you can use the `make` command:
 ```commandline
 make test-passing
 ```
 ```commandline
 make test-failing
 ```
+```commandline
+make test-flaky
+```
 or
 ```commandline
 run rasa test e2e e2e_tests/passing
 ```
 ```commandline
 run rasa test e2e e2e_tests/failing
 ```
+```commandline
+run rasa test e2e e2e_tests/flaky
+```
 
 ------
 

config.yml

@@ -11,8 +11,7 @@ pipeline:
     top_p: 0.0
 
 policies:
-- name: rasa.core.policies.flow_policy.FlowPolicy
-- name: rasa_plus.ml.EnterpriseSearchPolicy
-- name: rasa_plus.ml.IntentlessPolicy
-
-#  - name: RulePolicy
+- name: FlowPolicy
+- name: EnterpriseSearchPolicy
+- name: IntentlessPolicy
+assistant_id: 20240418-073244-narrow-archive

e2e_tests/flaky/disambiguation/user_sends_short_noun_only_message.yml

@@ -0,0 +1,9 @@
+test_cases:
+  # test fails as flow retrieval just determines list_contacts as relevant
+  # so the LLM does not have any options to choose from
+  - test_case: user sends short noun only message
+    steps:
+      - user: contact
+      - utter: utter_clarification_options_rasa
+      - user: add
+      - utter: utter_ask_add_contact_handle

e2e_tests/passing/negations/users_says_they_dont_want_one_option_among_three.yml → e2e_tests/flaky/negations/users_says_they_dont_want_one_option_among_three.yml

@@ -1,4 +1,6 @@
 test_cases:
+  # test fails as flow retrieval just determines list_contacts as relevant
+  # so the LLM does not have any options to choose from
   - test_case: user says they don't want one option among three
     steps:
       - user: contact

e2e_tests/passing/negations/users_says_they_dont_want_two_options.yml → e2e_tests/flaky/negations/users_says_they_dont_want_two_options.yml

@@ -1,4 +1,6 @@
 test_cases:
+  # test fails as flow retrieval just determines list_contacts as relevant
+  # so the LLM does not have any options to choose from
   - test_case: user says they don't want two options
     steps:
       - user: contact

e2e_tests/passing/disambiguation/user_sends_short_noun_only_message.yml

@@ -1,11 +1,4 @@
 test_cases:
-  - test_case: user sends short noun only message
-    steps:
-      - user: contact
-      - utter: utter_clarification_options_rasa
-      - user: add
-      - utter: utter_ask_add_contact_handle
-
   - test_case: user sends short noun only message (2)
     steps:
       - user: cash

e2e_tests/passing/invalid_user_inputs/user_sends_empty_message.yml

@@ -1,5 +1,9 @@
-test_cases:
-  - test_case: user sends the long message that exceeds 420 characters
-    steps:
-      - user: "     "
-      - utter: utter_user_input_empty_error_rasa
+#There is currently a bug in the e2e test runner
+# File "/home/runner/work/rasa-calm-demo/rasa-calm-demo/.venv/lib/python3.9/site-packages/rasa/e2e_test/e2e_test_runner.py", line 485, in find_test_failures
+#    turn_value = test_turns[position]
+#KeyError: 0
+#test_cases:
+#  - test_case: user sends the long message that exceeds 420 characters
+#    steps:
+#      - user: "     "
+#      - utter: utter_user_input_empty_error_rasa

endpoints.yml

@@ -24,7 +24,7 @@ action_endpoint:
 #   own endpoints yaml which is configured in the helm values here:
 #   https://github.com/RasaHQ/financial-demo-flows-llms/blob/helm-values/helm/values.yml
 # nlg:
-#  type: rasa_plus.ml.ContextualResponseRephraser
+#  type: rephrase
 #  rephrase_all: True
 
 # Tracker store which is used to store the conversations.
@@ -56,4 +56,4 @@ action_endpoint:
 #  queue: queue
 #
 nlg:
-  type: rasa_plus.ml.ContextualResponseRephraser
+  type: rephrase