-
Notifications
You must be signed in to change notification settings - Fork 146
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
Error on opening repo in a codespace or locally in devcontainer #3579
Comments
This happens because msal==1.20.0 requires cryptography<41. msal==1.22.0 would work with cryptography<43, unfortunately the latest version azure-cli-core requires msal==1.20.0. Fix : enforce cryptography<41 in
or from the AzureTRE-Deployment repository, add the following line at the end of
|
Thanks @jlabhard-sg . That works |
@marrobi Please re-open this and apply the fix to the repo |
@SvenAelterman reopened. If anybody has time to help with the fix would be appreciated. |
@marrobi I can create a PR for the fix provided by @jlabhard-sg if that's the right thing to do. (Confirmed it works, but I don't know if there's a better way to do it?) |
I have no better suggestions at present. If you can do a PR that would be very helpful and the team can review. |
I'm not clear why |
Transferring as fix needs to happen in Azure TRE repo. |
The error happens on building devcontainer, related to run
make install-cli
Please note, that we did not make any updates to repo, just started with a new docker installation and previously was running fine
#28 8.066 self.initialize_options() microsoft/AzureTRE#28 8.069 error: cryptography 41.0.1 is installed but cryptography<41,>=0.6 is required by {'msal'} microsoft/AzureTRE#28 8.099 2023-06-02 11:44:19.259Z: microsoft/AzureTRE#28 ERROR: executor failed running [/bin/bash -o pipefail -c make install-cli && echo -e "\n# Set up tre completion\nsource <(_TRE_COMPLETE=bash_source tre)" >> ~/.bashrc]: exit code: 2
I have also attached the full log:
creation.log
Steps to reproduce:
Or:
The text was updated successfully, but these errors were encountered: