[Obsolete] Patching required for a known issue in one of MONAI Deploy App SDK's dependencies #514
MMelQin
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Note this is obsolete after holoscan v2.9.0 was released on 01/26/2025, and the new version of holoscan CLI, now a standalone package, can also be downloaded and installed. See this announcement please.
One of the dependencies, the newly released Holoscan SDK v2,8.0, has a known issue, so a script is shown below to patch the pip installed Holoscan SDK in the virtual environment before the Holoscan v2.9 is released in February 2025.
This known issue is in the
holoscan/core/__init__.py
where theMultiMessageConditionInfo
was missed in theimport
, hence not visible when applications try to use it. This file is found in the site-packages oncemonai-deploy-app-sdk
is installed, e.g. at<virtual env>/lib/python3.10/site-packages/holoscan/core/__init__.py
.Further more, the MAP built with CLI packager will have this issue as the packager pulls the latest
holoscan~=2.0
from pypi,org as a dependency of monai-deploy-app-sdk, and MAP will again see runtime error. It has been further confirmed that both v2.7 and v2.8 of Holoscan SDK have this issue. To work around it, applications need to explicitly addholoscan~=2.6.0
in its requirements.txt file.Note if in the local environment pip installing Holoscan==2.6.0 after installing monai-deploy-app-sdk~=2.0, please patch the Holoscan CLI packager Dockerfile template, in the /holoscan/cli/packager/templates/Dockerfile.jinja2, to use a wildcard for versions of pip,
ENV PYTHON_PIP_VERSION=22.0.2+dfsg-*
. This same change was only made in Holoscan SDK v2.8 and onwards.It is a simple fix to patch holoscan v2.7 and v2.8 in local env, which can be done manually or by using the following script.
Beta Was this translation helpful? Give feedback.
All reactions