You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If Komodo releases are not located in /prog/res/komodo then trying to automatically use an env for a new komodoenv results in an error like:
/prog/res/komodo/2023.02.b3-py38-rhel7' is not a valid komodo release
In my case, the root is /prog/komodo/2023.02.b3-py38-rhel7.
Perhaps it's best to keep things super explicit, but it might be nice to try detecting the komodo root from the combination of KOMODO_RELEASE and PATH.
For reference, here's how we do this in komodo. (It would be even nicer if Komodo set an environment variable with the path to the root -- see linked issue.)
The text was updated successfully, but these errors were encountered:
As of #68 komodoenv first checks for the existence of /prog/komodo before defaulting to /prog/res/komodo, so should now be easier to use on Azure. Although this is not as robust as the suggestions in this issue.
If Komodo releases are not located in
/prog/res/komodo
then trying to automatically use an env for a newkomodoenv
results in an error like:/prog/res/komodo/2023.02.b3-py38-rhel7' is not a valid komodo release
In my case, the root is
/prog/komodo/2023.02.b3-py38-rhel7
.Perhaps it's best to keep things super explicit, but it might be nice to try detecting the komodo root from the combination of
KOMODO_RELEASE
andPATH
.For reference, here's how we do this in
komodo
. (It would be even nicer if Komodo set an environment variable with the path to the root -- see linked issue.)The text was updated successfully, but these errors were encountered: