v.2.7.0 ======= Improvements: ------------- #) [LUNA-8391] ``pynvcodec`` and ``pyfsdkinterop`` are no longer frozen: the new base images ship CUDA 12.4 and ``pynvcodec``/``pyfsdkinterop`` >= 3.1.6. #) [LUNA-8471] FSDK has been updated to 5.39.0. #) [LUNA-8649] The base docker images used for lambda creation have been moved to AlmaLinux 10. Lambdas with frozen old dependencies may stop working on the new base images, because the transition to the new CUDA and FSDK was performed. If updating a lambda's dependencies is not possible, use the ``LAMBDA_BASE_IMAGE`` setting (see `Base image chapter <../creation_pipeline.html#base-image>`_) to fix the previous base image for such lambdas. #) [LUNA-8716] The agent base image has been rebuilt on AlmaLinux 10. #) [LUNA-8783] The base docker images used for lambda creation can now be pinned in the platform settings. The new ``LAMBDA_BASE_IMAGE`` setting (see `Base image chapter <../creation_pipeline.html#base-image>`_) allows the platform to fix the base image (name and tag) that is used when the `create lambda <../_static/api.html#operation/createLambda>`_ request does not provide an explicit ``base_image`` parameter. The ``base_image`` passed in the request always takes precedence over the setting. .. warning:: Lambdas with frozen dependencies (a committed ``poetry.lock``) can break when the base image changes: the locked dependencies were resolved against the system packages of the old base image, and a new base image can ship different versions of the system dependencies (or not include them at all). To keep such lambdas working, take the old base image (name and tag) and either pin it in the ``LAMBDA_BASE_IMAGE`` setting or provide it explicitly in the ``base_image`` parameter of every create lambda request. Bugs fixed: ----------- #) [LUNA-8783] Lambda creation with a base image tag longer than 36 characters no longer fails with a 500 error. #) [LUNA-8783] An image build task is now stopped when the image creation times out (``IMAGE_CREATION_TIMEOUT``), instead of keeping running in the builder after the lambda is marked as failed. Migration: ---------- See a `migration <../migration.html>`_ manual.