-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Adding rdbms-connect fails with a pip error. #8264
Comments
Thank you for opening this issue, we will look into it. |
Same with This happens on Windows, in Ubuntu the extension can be installed |
This seems to be an issue for all extensions on python3.12 on windows 10/11 machines. |
I'm not able to repro this. what's the output of cd 'C:\Program Files\Microsoft SDKs\Azure\CLI2'
./python.exe -m pip install https://azcliprod.blob.core.windows.net/cli-extensions/rdbms_connect-1.0.7-py2.py3-none-any.whl --target ~\.azure\cliextensions\rdbms-connect I guess some dependency fails to build, which is a common issue on Windows and can't be fixed from our side. See: Azure/azure-cli#25067 (comment) |
The main problem is that an extension doesn't vendor all its dependencies. This makes it very difficult to guarantee that the extension build is reproducible, like in the case above where |
I'm glad the cause is found: @ambrahma for awareness. |
Describe the bug
On Windows 11 with Azure CLI version 2.66 running the command
az extension add --name rdbms-connect
results in the error:An error occurred. Pip failed with status code 3221225477. Use --debug for more information.
Related command
az extension add --name rdbms-connect
Errors
An error occurred. Pip failed with status code 3221225477. Use --debug for more information.
Issue script & Debug output
Expected behavior
That the extension is installed without error.
Environment Summary
Additional context
Previous versions of the azure cli would output the following in the debug log:
Removed configobj>=5.0.6 from https://files.pythonhosted.org/packages/f5/c4/c7f9e41bc2e5f8eeae4a08a01c91b2aea3dfab40a3e14b25e87e7db8d501/configobj-5.0.9.tar.gz (from pgcli==4.0.1->rdbms-connect==1.0.7)
And further investigation shows that configobj version 5.0.9 is the culprit, it is the package that breaks the installation. Trying previous version like 5.0.8 doesn't have any problems.
A possible workaround is to create a
constraints.txt
file with the contents:And then run the installation command manually like so, to make sure the configobj dependency is constrained to a version that still works:
The text was updated successfully, but these errors were encountered: