diff --git a/CHANGELOG.mdx b/CHANGELOG.mdx index d1290c72e19e..25f2fac539b6 100644 --- a/CHANGELOG.mdx +++ b/CHANGELOG.mdx @@ -199,7 +199,7 @@ Rasa 3.6.3 (2023-07-20) ### Bugfixes - [#12638](https://github.com/rasahq/rasa/issues/12638): Fix the issue with the most recent model not being selected if the owner or permissions where modified on the model file. -- [#12661](https://github.com/rasahq/rasa/issues/12661): Fixed `BlockingIOError` which occured as a result of too large data passed to strulogs. +- [#12661](https://github.com/rasahq/rasa/issues/12661): Fixed `BlockingIOError` which occurred as a result of too large data passed to strulogs. ### Improved Documentation - [#12659](https://github.com/rasahq/rasa/issues/12659): Update action server documentation with new capability to extend Sanic features by using plugins. @@ -1716,7 +1716,7 @@ Upgrade dependent libraries with security vulnerabilities (Pillow, TensorFlow, u by a factor of 3. - [#8801](https://github.com/rasahq/rasa/issues/8801): Change the confidence score assigned by [`FallbackClassifier`](components.mdx#fallbackclassifier) to fallback intent to be the same as the fallback threshold. - [#8926](https://github.com/rasahq/rasa/issues/8926): Issue a UserWarning if a specified **domain folder** contains files that look like YML files but cannot be parsed successfully. - Only invoked if user specifies a folder path in `--domain` paramater. Previously those invalid files in the specified folder were silently ignored. + Only invoked if user specifies a folder path in `--domain` parameter. Previously those invalid files in the specified folder were silently ignored. **Does not apply** to individually specified domain YAML files, e.g. `--domain /some/path/domain.yml`, those being invalid will still raise an exception. ### Bugfixes @@ -2530,7 +2530,7 @@ Upgrade dependent libraries with security vulnerabilities (Pillow, TensorFlow, u ### Improvements - [#3998](https://github.com/rasahq/rasa/issues/3998): Added a message showing the location where the failed stories file was saved. -- [#7232](https://github.com/rasahq/rasa/issues/7232): Add support for the top-level response keys `quick_replies`, `attachment` and `elements` refered to in `rasa.core.channels.OutputChannel.send_reponse`, as well as `metadata`. +- [#7232](https://github.com/rasahq/rasa/issues/7232): Add support for the top-level response keys `quick_replies`, `attachment` and `elements` referred to in `rasa.core.channels.OutputChannel.send_response`, as well as `metadata`. - [#7257](https://github.com/rasahq/rasa/issues/7257): Changed the format of the histogram of confidence values for both correct and incorrect predictions produced by running `rasa test`. - [#7284](https://github.com/rasahq/rasa/issues/7284): Run [`bandit`](https://bandit.readthedocs.io/en/latest/) checks on pull requests. Introduce `make static-checks` command to run all static checks locally. @@ -4386,7 +4386,7 @@ Upgrade dependent libraries with security vulnerabilities (Pillow, TensorFlow, u * [#5111](https://github.com/rasahq/rasa/issues/5111): Fixes `Exception 'Loop' object has no attribute '_ready'` error when running `rasa init`. -* [#5126](https://github.com/rasahq/rasa/issues/5126): Updated the end-to-end ValueError you recieve when you have a invalid story format to point +* [#5126](https://github.com/rasahq/rasa/issues/5126): Updated the end-to-end ValueError you receive when you have an invalid story format to point to the updated doc link. ## [1.6.1] - 2020-01-07 @@ -4394,7 +4394,7 @@ Upgrade dependent libraries with security vulnerabilities (Pillow, TensorFlow, u ### Bugfixes * [#4989](https://github.com/rasahq/rasa/issues/4989): Use an empty domain in case a model is loaded which has no domain - (avoids errors when accessing `agent.doman.`). + (avoids errors when accessing `agent.domain.`). * [#4995](https://github.com/rasahq/rasa/issues/4995): Replace error message with warning in tokenizers and featurizers if default parameter not set. @@ -5040,7 +5040,7 @@ Regression: changes from `1.2.12` were missing from `1.4.0`, readded them * evaluation of NER does not include 'no-entity' anymore -* `--successes` for `rasa test nlu` is now boolean values. If set incorrect/successful predictions +* `--successes` for `rasa test nlu` is now boolean values. If set, incorrect and successful predictions are saved in a file. * `--errors` is renamed to `--no-errors` and is now a boolean value. By default incorrect predictions are saved diff --git a/data/test_nlu_no_responses/sara_nlu_data.yml b/data/test_nlu_no_responses/sara_nlu_data.yml index 9d83ce3efd02..bcb2f2359d55 100644 --- a/data/test_nlu_no_responses/sara_nlu_data.yml +++ b/data/test_nlu_no_responses/sara_nlu_data.yml @@ -2050,16 +2050,16 @@ nlu: - what is the latest version of rasa? - Can I use Rasa for E-Mail - Can you send messages based on events? - - How did rasa works? + - How does Rasa work? - How do I use ngrok with [rasa x](product)? - I want to know more about tracker - What is the difference between entities and slots? - Where can I get the source code of Rasa? - Which other tools can be used to create chatbots? - - an I use Rasa for e-mail applications + - Can I use Rasa for e-mail applications - any open source GUI rasa have? - any other tools to create chatbots? - - can i install on may mac + - can i install on my mac - can rasa run standalone - db processing - do you have docker image for rasa? @@ -2153,9 +2153,9 @@ nlu: - php - php code - what is the difference between slot and entity - - is slot teh same as entity + - is slot the same as entity - what should I do when I want to use a binary slot - - How d I use a boolean slot + - How do I use a boolean slot - what are values of a boolean slot - fallback - stories files diff --git a/docs/static/spec/action-server.yml b/docs/static/spec/action-server.yml index 67fabda8ab0d..074e261c243a 100644 --- a/docs/static/spec/action-server.yml +++ b/docs/static/spec/action-server.yml @@ -42,7 +42,7 @@ paths: $ref: "./rasa.yml#/components/schemas/Domain" responses: 200: - description: Action was executed succesfully. + description: Action was executed successfully. content: application/json: schema: diff --git a/docs/static/spec/rasa.yml b/docs/static/spec/rasa.yml index a329999d0b32..2f76bf7639d5 100644 --- a/docs/static/spec/rasa.yml +++ b/docs/static/spec/rasa.yml @@ -792,7 +792,7 @@ paths: Unloads the currently loaded trained model from the server. responses: 204: - description: Model was sucessfully unloaded. + description: Model was successfully unloaded. 401: $ref: '#/components/responses/401NotAuthenticated' 403: diff --git a/rasa/nlu/test.py b/rasa/nlu/test.py index ae04060ddb5d..6309cf68e901 100644 --- a/rasa/nlu/test.py +++ b/rasa/nlu/test.py @@ -1532,7 +1532,7 @@ async def combine_result( data: training data intent_results: intent evaluation results entity_results: entity evaluation results - response_selection_results: reponse selection evaluation results + response_selection_results: response selection evaluation results Returns: intent, entity, and response selection metrics """ diff --git a/test_environments/message_and_event_brokers/kafka/sasl_plain/with_tls/ssl_all_conections/README.md b/test_environments/message_and_event_brokers/kafka/sasl_plain/with_tls/ssl_all_conections/README.md index 9b6faccd8851..31b135ee440b 100644 --- a/test_environments/message_and_event_brokers/kafka/sasl_plain/with_tls/ssl_all_conections/README.md +++ b/test_environments/message_and_event_brokers/kafka/sasl_plain/with_tls/ssl_all_conections/README.md @@ -14,8 +14,8 @@ Client should also import this certificate to verify the identity of the Kafka b * `ca-key` - CA private key (used to generate CA certificate `ca-cert`) * `cert-request` - certificate request for the broker, it must be signed by the CA before it can be used * `signed-server-cert` - signed certificate for the broker, it must be imported into the keystore -* `ssl_keystore_password` - file containing the password for the keystore -* `ssk_key_password` - file containing the password for the CA private key, used to unlock the CA certificate +* `ssl_keystore_credentials` - file containing credentials for the keystore +* `ssl_key_credentials` - file containing credentials for the CA private key, used to unlock the CA certificate * `broker_jaas.conf` - JAAS configuration file for the broker, contains usernames and passwords a client can use to authenticate diff --git a/test_environments/message_and_event_brokers/kafka/sasl_plain/with_tls/ssl_localhost/README.md b/test_environments/message_and_event_brokers/kafka/sasl_plain/with_tls/ssl_localhost/README.md index e9b5c685e636..a7a4e16adccb 100644 --- a/test_environments/message_and_event_brokers/kafka/sasl_plain/with_tls/ssl_localhost/README.md +++ b/test_environments/message_and_event_brokers/kafka/sasl_plain/with_tls/ssl_localhost/README.md @@ -11,8 +11,8 @@ Client should also import this certificate to verify the identity of the Kafka b * `ca-key` - CA private key (used to generate CA certificate `ca-cert`) * `cert-request` - certificate request for the broker, it must be signed by the CA before it can be used * `signed-server-cert` - signed certificate for the broker, it must be imported into the keystore -* `ssl_keystore_password` - file containing the password for the keystore -* `ssk_key_password` - file containing the password for the CA private key, used to unlock the CA certificate +* `ssl_keystore_credentials` - file containing credentials for the keystore +* `ssl_key_credentials` - file containing credentials for the CA private key, used to unlock the CA certificate * `broker_jaas.conf` - JAAS configuration file for the broker, contains usernames and passwords a client can use to authenticate ## How to generate certificates for TLS bound to DNS localhost @@ -24,7 +24,7 @@ Refer to [this](../README.md#about-certificates) section for more details about You can create the certificates and store them in the keystore using the following commands: ```shell -# Create private and public key (public key is usually reffered to as Certificate Authority's certificate or CA certificate) +# Create private and public key (public key is usually referred to as Certificate Authority's certificate or CA certificate) openssl req -x509 -newkey rsa:4096 -keyout ca-key -out ca-cert -days 365 -nodes -subj '/CN=localhost/OU=Atom/O=Rasa/L=Berlin/ST=Germany/C=GE' -passin pass:123456 -passout pass:123456 # Create server keystore protected with storepass and keypass diff --git a/test_environments/message_and_event_brokers/kafka/sasl_scram/with_tls/README.md b/test_environments/message_and_event_brokers/kafka/sasl_scram/with_tls/README.md index e195d7303717..5aa68eff9b55 100644 --- a/test_environments/message_and_event_brokers/kafka/sasl_scram/with_tls/README.md +++ b/test_environments/message_and_event_brokers/kafka/sasl_scram/with_tls/README.md @@ -88,7 +88,7 @@ Client will use the CA certificate to verify the identity of the Kafka broker. You can create the certificates and store them in the keystore using the following commands: ```shell -# Create private and public key (public key is usually reffered to as Certificate Authority's certificate or CA certificate) +# Create private and public key (public key is usually referred to as Certificate Authority's certificate or CA certificate) openssl req -x509 -newkey rsa:4096 -keyout ca-key -out ca-cert -days 365 -nodes -subj '/CN=localhost/OU=Atom/O=Rasa/L=Berlin/ST=Germany/C=GE' -passin pass:123456 -passout pass:123456 # Create server keystore protected with storepass and keypass