3.5.4 Release Notes#
Features#
New ‘Community 360’ role for dashboards. Allows having a dedicated dashboard to display contextual data based on a selected community.
Added a new API endpoint to fetch detailed information surrounding a community such as the number of subscribers and the number of items belonging to the community.
[GroundtruthLabelling] Show message when rule query has more than 20 words
[StudioPlugin] Adds error handling for model deletion
In the groundtruth labelling page, if there are unprocessed feedbacks the feedback tab will have a dot on top
New React Community Header widget.
Hide edit and delete buttons for the read only workflows and allow to only clone it.
Extend possible package size sending to MariaDB server. It resolves problems when big amount of data (like file with synonyms) breaks the SQL server.
It is now possible to define a rule_field field which will contain the rule which triggered the match. If now rule matches, it will save the vale of the no_rule_matched_label field which defaults to NO_RULE_MATCHED.
Struct logger is now enabled for classifiers’ templates
Update frontend to use the new smart cropping for suggested images.
When giving feedback to an entity, label select will now show all labels with model name for same tagging level
Expose cloning ML workflows to the API. Now the ML workflow can be cloned using the Squirro Client.
Add initial version of the PDF Conversion service (currently available only in the Docker-based dev envs, it is not packaged yet).
Bug Fixes#
Add react to labelling ListView to prevent tooltip render fail
Fix dependency error related to spacy version and building libnlp
Fix overwriting steps structure
Handle empty suggestion from pexel.
[Data Sources] Fixed sorting and pagination issues, plus eminating problems (inability to edit etc)
Fix condition for read tooltip
Fix bug in status aggregator which prevented from counting data source batches properly
Breaking Changes#
ML service has spare processes
GroundTruth rule cannot have more than 20 words
Installation and Upgrade#
You will have to resolve at least the following config files when upgrading from Squirro 3.3.0
/etc/nginx/conf.d/ssl.inc
/etc/squirro/common.ini
For new installations, please follow the Installing Squirro on Linux instructions.
To upgrade an existing installation, please consult Upgrading Squirro.