Skip to content

v.5.137.0#

Changes

  • SDK has been updated to version 5.32.0.

    In this version:

    • Deepfake estimator has been updated to version 10
    • OneShotLiveness estimator has been updated to version 13
    • HeadPoseEstimator estimator has been updated to version 4

  • A folder system — a new way of organizing files — has been made available in the /images and /objects resources.

    The existing method of storing images and objects as a list now includes the ability to create structured storage with nested folders. This allows you to group files into logical categories (for example, for analyzing neural network errors, incidents, or storing related data).

    Basic operations for the /images and /objects resources when working with folders:

    1. Creating and deleting folders (along with their contents).
    2. Getting information about a folder and checking its existence.
    3. Working with files within folders:
    4. uploading files with automatic creation of subfolders (for example, when uploading a file to the path 6/images/folder/subfolder1/subfolder2/filename, the system will create the missing subfolder1 and subfolder2 folders, and the root folder folder must already be created).
    5. getting and checking the existence of files.
    6. deleting subfolders and files.
    7. Getting a list of files in a folder.
    8. Copying files and folders (only within the same resource type).

    Key features of working with folders:

    • account isolation – each folder belongs to a specific account. The same access tokens are used for folder operations as for working with the /images and /objects resources.
    • works with both local disks and S3 storage. Note: In S3 storage, "folders" are logical groupings of files based on the prefixes in their names. For example, the file folder/file.txt will appear as being in the folder folder, although physically, that's just part of its name.

    For a full list of new requests for working with folders, see the resources /images and /objects.

  • Stream management capabilities through groups have been extended.

    Previously, stream grouping only allowed you to start, stop, and delete streams. Now, stream groups can contain shared settings (stream_settings) and analytics (analytics), which are automatically applied to all linked streams according to merge rules. This allows you to:

    • simplify the setup of multiple streams;
    • centrally manage analytics for camera groups.

    For more information on the merge rules and usage scenarios, see "Stream grouping".

  • The Guardant utility version in the LUNA PLATFORM distribution has been updated from version 3.29 to 4.4.3.

  • Filtering candidates by event source groups has been added to general events matching request.

    The source_groups parameter can now be used to limit the search for candidates to only those generalized events that belong to the specified groups.

    See the "Event source groups" section.

Fixed errors

  • Now when deleting lambda the system also tries to delete its image from the Docker registry.

    To do this, the image manifest is deleted in the background. This operation is only performed if the delete feature is enabled in the Docker registry (storage.delete.enabled). If deletion is not possible, the system logs an error in the monitoring database (the lambda_errors series). Successful manifest deletion is also stored in the monitoring database.

    Note: After deleting the manifest, the image becomes unavailable and will be deleted the next time the garbage collection task runs in the registry.

    For more information, see the Lambda usage section of the developer guide.