Skip to content

Releases: RasaHQ/rasa

1.9.5

02 Apr 08:55
8063f79
Compare
Choose a tag to compare

Improvements

  • #5533: Support for
    PostgreSQL schemas 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

    CREATE SCHEMA schema_name;
    

Bugfixes

  • #5547: Fixed ambiguous logging in DIETClassifier by adding the name of the calling class to the log message.

1.9.4

30 Mar 19:19
bb61718
Compare
Choose a tag to compare

Bugfixes

  • #5529: Fix memory leak problem on increasing number of calls to /model/parse endpoint.

1.9.3

27 Mar 12:30
805de56
Compare
Choose a tag to compare

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.8.3

27 Mar 14:42
ba5e544
Compare
Choose a tag to compare

Bugfixes

  • #5405: Fixes issue where model always gets retrained if multiple NLU/story files are in a
    directory, by sorting the list of files.
  • #5444: Fixed ambiguous logging in DIETClassifier by adding the name of the calling class to the log message.
[\#5506](https://github.com/rasahq/rasa/issues/5506): 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 or `rasa>=1.9.3` and re-train their models if `ResponseSelector` was used in their pipeline.

Improved Documentation

  • #5302: Improved documentation on how to build and deploy an action server image for use on other servers such as Rasa X deployments.

1.9.2

26 Mar 12:45
77e97de
Compare
Choose a tag to compare

Improved Documentation

  • #5497: Fix documentation to bring back Sara.

1.9.1

25 Mar 22:50
336bc8b
Compare
Choose a tag to compare

Bugfixes

  • #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

24 Mar 21:34
d946368
Compare
Choose a tag to compare

Features

  • #5006: Channel hangouts for Rasa integration with Google Hangouts Chat is now supported out-of-the-box.

  • #5389: Add an optional path to a specific directory to download and cache the pre-trained model weights for HFTransformersNLP.

  • #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: 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: 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: 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
    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:

    event_broker:
      type: pika
      url: localhost
      username: username
      password: password
      queues:
        - queue-1
        - queue-2
        - queue-3
    
  • #5416: Change rasa init to include tests/conversation_tests.md file by default.

  • #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: 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: 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: 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: Fixed bug where FallbackPolicy would always fall back if the fallback action is
    action_listen.

  • #5361: Fixed bug where starting or ending a response with \n\n led to one of the responses returned being empty.

  • #5405: Fixes issue where model always gets retrained if multiple NLU/story files are in a
    directory, by sorting the list of files.

  • #5444: Fixed ambiguous logging in DIETClassifier by adding the name of the calling class to the log message.

Improved Documentation

  • #2237: Restructure the "Evaluating models" documentation page and rename this page to testing-your-assistant.
  • #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

1.8.2

19 Mar 14:22
b53024d
Compare
Choose a tag to compare

Bugfixes

  • #5438: Fixed bug when installing rasa with poetry.
  • #5413: Fixed bug with EmbeddingIntentClassifier, where results
    weren't the same as in 1.7.x. Fixed by setting weight sparsity to 0.

Improved Documentation

  • #5404: Explain how to run commands as root user in Rasa SDK Docker images since version
    1.8.0. Since version 1.8.0 the Rasa SDK Docker images does not longer run as
    root user by default. For commands which require root user usage, you have to
    switch back to the root user in your Docker image as described in
    deploying-your-rasa-assistant_custom-dependencies.
  • #5402: Made improvements to Building Assistants tutorial

1.8.1

07 Mar 11:57
fcc0d42
Compare
Choose a tag to compare

Bugfixes

  • #5354: Fixed issue with using language models like xlnet along with entity_recognition set to True inside DIETClassifier.

Miscellaneous internal changes

1.7.4

25 Feb 08:55
bf79fe9
Compare
Choose a tag to compare
patch release fixing duplicate  events