Rasa

- [7695](https://github.com/rasahq/rasa/issues/7695): Ignore checking that intent is in domain for E2E story utterances when running `rasa data validate`. Previously data validation would fail on E2E stories.
- [8711](https://github.com/rasahq/rasa/issues/8711): Fix for unnecessary retrain and duplication of folders in the model

Bugfixes
- [7286](https://github.com/rasahq/rasa/issues/7286): Best model checkpoint allows for metrics to be equal to previous best if at least one
metric improves, rather than strict improvement for each metric.
- [8200](https://github.com/rasahq/rasa/issues/8200): Fixes a bug where multiple plots overlap each other and are rendered incorrectly when comparing performance across multiple NLU pipelines.
- [8812](https://github.com/rasahq/rasa/issues/8812): Don't evaluate entities if no entities present in test data.

Also, catch exception in `plot_paired_histogram` when data is empty.

Improvements
- [7691](https://github.com/rasahq/rasa/issues/7691): Changed the default config to train the `RulePolicy` before the `TEDPolicy`.
This means that conflicting rule/stories will be identified before a potentially slow training of the `TEDPolicy`.
- [7799](https://github.com/rasahq/rasa/issues/7799): Updated validator used by `rasa data validate` to verify that actions used in stories and rules are present in the domain and that form slots match domain slots.
- [7912](https://github.com/rasahq/rasa/issues/7912): Rename `plot_histogram` to `plot_paired_histogram` and fix missing bars in the plot.
- [8225](https://github.com/rasahq/rasa/issues/8225): Changed --data option type in the ``rasa data validate command to allow more than one path to be passed.

Bugfixes
- [8152](https://github.com/rasahq/rasa/issues/8152): The file `failed_test_stories.yml` (generated by `rasa test`) now also includes the wrongly predicted entity as a comment next to the entity of a user utterance.
Additionally, the comment printed next to the intent of a user utterance is printed only if the intent was wrongly predicted (irrelevantly if there was a wrongly predicted entity or not in the specific user utterance).
- [8309](https://github.com/rasahq/rasa/issues/8309): Added check in PikaEventBroker constructor: if port cannot be cast to integer, raise RasaException
- [8388](https://github.com/rasahq/rasa/issues/8388): Fixed bug where missing intent warnings appear when running `rasa test`
- [8611](https://github.com/rasahq/rasa/issues/8611): Update `should_retrain` function to return the correct fingerprint comparison result
even when there is a problem with model unpacking.
- [8719](https://github.com/rasahq/rasa/issues/8719): Handle correctly Telegram edited message.

Miscellaneous internal changes
- [8591](https://github.com/rasahq/rasa/issues/8591), [#8641](https://github.com/rasahq/rasa/issues/8641), [#8654](https://github.com/rasahq/rasa/issues/8654), [#8658](https://github.com/rasahq/rasa/issues/8658), [#8802](https://github.com/rasahq/rasa/issues/8802)

Bugfixes
- [8046](https://github.com/rasahq/rasa/issues/8046): `ResponseSelector` can now be trained with the transformer enabled (i.e. when a positive
`number_of_transformer_layers` is provided) even if one doesn't specify the transformer's
size. Previously, not specifying `transformer_size` led to an error.
- [8386](https://github.com/rasahq/rasa/issues/8386): Return `EntityEvaluationResult` during evaluation of test stories only if `parsed_message` is not `None`.
- [8546](https://github.com/rasahq/rasa/issues/8546): Ignore `OSError` in Sentry reporting.
- [8547](https://github.com/rasahq/rasa/issues/8547): Replaced `ValueError` with `RasaException` in TED model `_check_data` method.
- [8639](https://github.com/rasahq/rasa/issues/8639): Changed import to fix agent creation in Jupyter.

Miscellaneous internal changes
- [7906](https://github.com/rasahq/rasa/issues/7906), [#8544](https://github.com/rasahq/rasa/issues/8544), [#8725](https://github.com/rasahq/rasa/issues/8725), [#8726](https://github.com/rasahq/rasa/issues/8726), [#8727](https://github.com/rasahq/rasa/issues/8727), [#8728](https://github.com/rasahq/rasa/issues/8728)

Bugfixes
- [8364](https://github.com/rasahq/rasa/issues/8364): Fixed a bug where [`ListSlot`](domain.mdx#list-slot)s were filled with single items
in case only one matching entity was extracted for this slot.

Values applied to [`ListSlot`](domain.mdxlist-slot)s will be converted to a `List`
in case they aren't one.
- [8581](https://github.com/rasahq/rasa/issues/8581): Fix bug with false rule conflicts

This essentially reverts [PR 8446](https://github.com/RasaHQ/rasa/pull/8446/files), except for the tests.
The PR is redundant due to [PR 8646](https://github.com/RasaHQ/rasa/pull/8646/files).
- [8590](https://github.com/rasahq/rasa/issues/8590): Handle `AttributeError ` thrown by empty slot mappings in domain form through refactoring.
- [8631](https://github.com/rasahq/rasa/issues/8631): Fixed incorrect `The action 'utter_<response selector intent>' is used in the stories, but is not a valid utterance action`
error when running `rasa data validate` with response selector responses in the domain file.

Improved Documentation
- [8079](https://github.com/rasahq/rasa/issues/8079): Added a note to clarify best practice for resetting all slots after form deactivation.

Miscellaneous internal changes
- [8587](https://github.com/rasahq/rasa/issues/8587)

Bugfixes
- [7908](https://github.com/rasahq/rasa/issues/7908): Made `SchemaError` message available to validator so that the reason why reason schema validation fails during `rasa data validate` is displayed when response `text` value is `null`.
Added warning message when deprecated MappingPolicy format is used in the domain.
- [8623](https://github.com/rasahq/rasa/issues/8623): When there are multiple entities in a user message, they will get sorted when creating a
representation of the current dialogue state.

Previously, the ordering was random, leading to inconsistent state representations. This
would sometimes lead to memoization policies failing to recall a memorised action.