Skip to content

LUNA PLATFORM v.5.42.0#

Changes#

  • Now the Image Store service can store any files as objects (for example, a video file).

    Previously, only the following types of objects were available: json, text, zip, pdf.

    You can upload files using the "create objects" request. The bytes of the file must be specified in the request body, and the Content-Type header must contain the MIME type of the file (for example, video/mp4). The response to the "get object" request contains the header Content-Disposition. This header contains the file name of the attachment object (for example, video_1.mp4). The file name is generated based on the object_id and the MIME type.

    If the MIME type of the file could not be determined, then the file extension will be set as `.bin'.

    Now the Accept header is ignored for the "get object" request. Previously, the service returned the error 12023, Content type is unacceptable with the status code 406, if the object content type did not match the MIME type of the file.

  • Now, when executing any request with correct authorization, information about the corresponding account is displayed in the logs of the API service.

    This functionality enables you to determine who exactly executed a particular request. This may be required for information security and system administrators.

    If the request was executed with BasicAuth or LunaAccountIdAuth type authorization, the following message will be displayed in the logs:

    Request invoked by user (account_id: '270531af-e52e-4538-9181-628d9900a0db')

    If the request was executed with BearerAuth type authorization, the following message will be displayed in the logs:

    Request invoked by user (account_id: '270531af-e52e-4538-9181-628d9900a0db' token_id: 'd57e16f5-e243-47d2-aa85-8b200c12d86f')

    If the request was executed without authorization, the following message will be displayed in the logs:

    Request invoked by user (account_id: null)

    The logs of the Accounts service additionally display information about the creation of tokens by specific users:

    User with account_id: '270531af-e52e-4538-9181-628d9900a0db' create token: 'd57e16f5-e243-47d2-aa85-8b200c12d86f'

    Logging information about the creation of tokens enables you to track where the token came from and which user it belonged to, even after it was deleted.

  • A new check shoulders_position has been added to the face_quality and iso sections, which determines the most predominant state of the shoulder position from the following:

    • non-parallel
    • parallel
    • hidden

  • The execution of the "get faces" request with all target fields has been sped up.

  • The memory usage by the Task service has been reduced in some cases of using the "Cross-matching" task.

Fixed errors#

  • Fixed an error where the script db_create.py didn't work for non-default configuration values of the Configurator service.

  • Fixed an error where the cache warmed up when starting the Python Matcher service with the "DESCRIPTORS_CACHE" setting turned off.

  • Fixed an error where the Python Matcher service started and continued to work when some workers stopped with an error.

    A "worker" is the Python Matcher service process that handles incoming (HTTP) requests.

  • Fixed behavior that could result in the deletion of one or all new event subscriptions if the new subscription was created and the old one was deleted at the same time.

  • Fixed an error where using EXIF data evaluation (parameter use_exif_info) could lead to an error of the form Internal server error.

r