Rasa

Latest version: v3.6.20

Safety actively analyzes 679777 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 42 of 49

1.9.5

Not secure
Improvements
============

- [\5533](https://github.com/rasahq/rasa/issues/5533): Support for
[PostgreSQL schemas](https://www.postgresql.org/docs/11/ddl-schemas.html) in
sql-tracker-store. The `SQLTrackerStore`
accesses schemas defined by the `POSTGRESQL_SCHEMA` environment variable if
connected to a PostgreSQL database.

The schema is added to the connection string option's `-csearch_path` key, e.g.
`-options=-csearch_path=<SCHEMA_NAME>` (see
<https://www.postgresql.org/docs/11/contrib-dblink-connect.html> for more details).
As before, if no `POSTGRESQL_SCHEMA` is defined, Rasa uses the database's default
schema (`public`).

The schema has to exist in the database before connecting, i.e. it needs to have been
created with

{.sourceCode .postgresql}
CREATE SCHEMA schema_name;


Bugfixes
========

- [\5547](https://github.com/rasahq/rasa/issues/5547): Fixed ambiguous logging in `DIETClassifier` by adding the name of the calling class to the log message.

1.9.4

Not secure
Bugfixes
========

- [\5529](https://github.com/rasahq/rasa/issues/5529): Fix memory leak problem on increasing number of calls to `/model/parse` endpoint.

1.9.3

Not secure
Bugfixes
========

-

[\5505](https://github.com/rasahq/rasa/issues/5505): Set default value for `weight_sparsity` in `ResponseSelector` to `0`.

: This fixes a bug in the default behaviour of `ResponseSelector` which was accidentally introduced in `rasa==1.8.0`.
Users should update to this version and re-train their models if `ResponseSelector` was used in their pipeline.

1.9.2

Not secure
Improved Documentation
======================

- [\5497](https://github.com/RasaHQ/rasa/pull/5497): Fix documentation to bring back Sara.

1.9.1

Not secure
Bugfixes
========

- [\5492](https://github.com/rasahq/rasa/issues/5492): Fix an issue where the deprecated `queue` parameter for the event-brokers-pika
was ignored and Rasa Open Source published the events to the `rasa_core_events`
queue instead. Note that this does not change the fact that the `queue` argument
is deprecated in favor of the `queues` argument.

1.9.0

Not secure
Features
========

- [\5006](https://github.com/rasahq/rasa/issues/5006): Channel `hangouts` for Rasa integration with Google Hangouts Chat is now supported out-of-the-box.
- [\5389](https://github.com/rasahq/rasa/issues/5389): Add an optional path to a specific directory to download and cache the pre-trained model weights for HFTransformersNLP.
- [\5422](https://github.com/rasahq/rasa/issues/5422): Add options `tensorboard_log_directory` and `tensorboard_log_level` to `EmbeddingIntentClassifier`,
`DIETClasifier`, `ResponseSelector`, `EmbeddingPolicy` and `TEDPolicy`.

By default `tensorboard_log_directory` is `None`. If a valid directory is provided,
metrics are written during training. After the model is trained you can take a look
at the training metrics in tensorboard. Execute `tensorboard --logdir <path-to-given-directory>`.

Metrics can either be written after every epoch (default) or for every training step.
You can specify when to write metrics using the variable `tensorboard_log_level`.
Valid values are 'epoch' and 'minibatch'.

We also write down a model summary, i.e. layers with inputs and types, to the given directory.

Improvements
============

- [\4756](https://github.com/rasahq/rasa/issues/4756): Make response timeout configurable.
`rasa run`, `rasa shell` and `rasa x` can now be started with
`--response-timeout <int>` to configure a response timeout of `<int>` seconds.
- [\4826](https://github.com/rasahq/rasa/issues/4826): Add full retrieval intent name to message data
`ResponseSelector` will now add the full retrieval intent name
e.g. `faq/which_version` to the prediction, making it accessible
from the tracker.
- [\5258](https://github.com/rasahq/rasa/issues/5258): Added `PikaEventBroker` (event-brokers-pika) support for publishing to
multiple queues. Messages are now published to a `fanout` exchange with name
`rasa-exchange` (see
[exchange-fanout](https://www.rabbitmq.com/tutorials/amqp-concepts.html#exchange-fanout)
for more information on `fanout` exchanges).

The former `queue` key is deprecated. Queues should now be
specified as a list in the `endpoints.yml` event broker config under a new key
`queues`. Example config:

{.sourceCode .yaml}
event_broker:
type: pika
url: localhost
username: username
password: password
queues:
- queue-1
- queue-2
- queue-3


- [\5416](https://github.com/rasahq/rasa/issues/5416): Change `rasa init` to include `tests/conversation_tests.md` file by default.
- [\5446](https://github.com/rasahq/rasa/issues/5446): The endpoint `PUT /conversations/<conversation_id>/tracker/events` no longer
adds session start events (to learn more about conversation sessions, please
see session\_config) in addition to the events which were sent in the request
payload. To achieve the old behavior send a
`GET /conversations/<conversation_id>/tracker`
request before appending events.
- [\5482](https://github.com/rasahq/rasa/issues/5482): Make `scale_loss` for intents behave the same way as in versions below `1.8`, but
only scale if some of the examples in a batch has probability of the golden label more than `0.5`.
Introduce `scale_loss` for entities in `DIETClassifier`.

Bugfixes
========

- [\5205](https://github.com/rasahq/rasa/issues/5205): Fixed the bug when FormPolicy was overwriting MappingPolicy prediction (e.g. `/restart`).
Priorities for mapping-policy and form-policy are no longer linear:
`FormPolicy` priority is 5, but its prediction is ignored if `MappingPolicy` is used for prediction.
- [\5215](https://github.com/rasahq/rasa/issues/5215): Fixed issue related to storing Python `float` values as `decimal.Decimal` objects
in DynamoDB tracker stores. All `decimal.Decimal` objects are now converted to
`float` on tracker retrieval.

Added a new docs section on tracker-stores-dynamo.
- [\5356](https://github.com/rasahq/rasa/issues/5356): Fixed bug where `FallbackPolicy` would always fall back if the fallback action is
`action_listen`.
- [\5361](https://github.com/rasahq/rasa/issues/5361): Fixed bug where starting or ending a response with `\n\n` led to one of the responses returned being empty.
- [\5405](https://github.com/rasahq/rasa/issues/5405): Fixes issue where model always gets retrained if multiple NLU/story files are in a
directory, by sorting the list of files.
- [\5444](https://github.com/rasahq/rasa/issues/5444): Fixed ambiguous logging in DIETClassifier by adding the name of the calling class to the log message.

Improved Documentation
======================

- [\2237](https://github.com/rasahq/rasa/issues/2237): Restructure the "Evaluating models" documentation page and rename this page to testing-your-assistant.
- [\5302](https://github.com/rasahq/rasa/issues/5302): Improved documentation on how to build and deploy an action server image for use on other servers such as Rasa X deployments.

Miscellaneous internal changes
==============================

- \5340

Page 42 of 49

Links

Releases

Has known vulnerabilities

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.