-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ML Extension 2.30.0 responds with: 'ml' is misspelled or not recognized by the system
when triggered.
#29940
Comments
Hi @yogeshg, 2.60.0 is not the latest Azure CLI(2.64.0). If you haven't already attempted to do so, please upgrade to the latest Azure CLI version by following https://learn.microsoft.com/en-us/cli/azure/update-azure-cli. |
Thank you for opening this issue, we will look into it. |
Here are some similar issues that might help you. Please check if they can solve your problem.
|
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @azureml-github. |
I'm facing the same issue after upgrade
|
Started to see same error since yesterday, even with older versions ( Created this ticket in |
Since today we have started seeing the same issues. Both on windows machines and in our devops pipelines. |
Similar issue on our end, it was all working fine yesterday but now running into this issue. |
Also seeing since today (2024-09-20) |
Also seeing it since today (2024-09-20) |
Same here. My Azure devops pipelines are broken. Even if I specify previous version of ml 2.29.0. Found that pipeline was working with OS: Ubuntu 22.04.4 LTS. Now pool returns Ubuntu 22.04.5 LTS. Code of pipeline the same. The only thing environment changed. I have tried
Nothing changed - the same error.
YAML code:
|
It appears that there is some intermingling of dependencies. Do extension Python package dependencies consider the base azure-cli dependencies when installed? Looking at where CLI extension dependencies are installed for me, ( I think something may need updating in the dependency resolution logic when installing an extension. Ideally, azure-cli extension Python requirements should remain compatible with the base azure-cli requirements when the extension is installed (i.e. azure-identity 1.17.1 should automatically have been installed with the ML extension). The workaround is to install an older version of azure-identity in whatever virtual environment azure-cli is using. Example workarounds: Linux: sudo /opt/az/bin/python3 -m pip install azure-identity==1.17.1 Windows (in elevated/administrator terminal): C:\"Program Files (x86)"\"Microsoft SDKs"\Azure\CLI2\python.exe -m pip install azure-identity==1.17.1 Not sure about Mac, but probably just need to run the python executable somewhere in I think you can glean the location of the environment your azure-cli is using based on the error message:
|
Thanks @pvaneck I am trying out the workaround, and seems promising. I tried pinning the cli and the extension versions y'day, but was seeing the issue with older versions too, just like this report. Thanks for debugging and explaining the issue, now it makes sense why even the older versions would be broken. I hope you can address the root cause by updating the packaging strategy, perhaps syncing the release cadence of the Azure CLI and its extensions. Python dependency hell is well-named for a reason! |
It's resolved by Azure/azure-cli-extensions#8006 |
It is by design that packages installed by base Azure CLI take precedence. Previously, there was a PR #12778 to prioritize packages installed by extensions, but it was rejected as explained in #12778 (comment). The base Azure CLI has no dependency on
We have to bump to |
In Ubuntu, for doing this manually (until updated APT packages are publicly available), you can execute the commands published in #30209 (comment) : sudo /opt/az/bin/python3 -m pip install \
azure-core==1.31.0 \
azure-identity==1.18.0 |
Describe the bug
ML Extension 2.30.0 responds with:
'ml' is misspelled or not recognized by the system
when triggered.Related command
Errors
Issue script & Debug output
Expected behavior
It should return the error message.
Environment Summary
I am using this in mac os. M3 machine
Additional context
No response
The text was updated successfully, but these errors were encountered: