Closed dyudyunov closed 9 months ago
Thanks for the pull request, @dyudyunov! Please note that it may take us up to several weeks or months to complete a review and merge your PR.
Feel free to add as much of the following information to the ticket as you can:
All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.
Please let us know once your PR is ready for our review and all tests are green.
Hi @edx-secure @adzuci! Would someone be able to please review / merge this for us? There is also a backport.
Hi @edx-secure @adzuci! Would someone be able to please review / merge this for us? There is also a backport.
Hi @edx-secure @adzuci! Following up on this. :)
@Agrendalath @xitij2000 Have we seen this error before? Any concerns about this solution?
@pomegranited, yes, we're just pinning retirement_service_pip_version: 21.2.1
, which matches the version used here. If the newer version works, then it's even better. 👍🏻 from me.
@dyudyunov 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future.
With the current version of the pip (19.0.3) it is impossible to install the cryptography package with a version higher than 39.X.X (starting from the palm release it is 40+, source: https://github.com/openedx/tubular/blob/open-release/palm.3/requirements/base.txt#L47)
The issue could be resolved by either installing the rustc to build the package or upgrading the pip version to use the prebuild wheel which is the recommendation from the cryptography setup guide: https://cryptography.io/en/latest/installation/#building-cryptography-on-linux
In this PR I increased the pip version using the version pinned in the tubular requirements: https://github.com/openedx/tubular/blob/master/requirements/pip.txt#L11
The pip version installation described here https://github.com/openedx/configuration/blob/master/playbooks/roles/user_retirement_pipeline/tasks/main.yml#L34
Notes
Installing requirements from the
requirements/pip.txt
file instead of pinning the pip version in the configuration seems to be a better solution for me, but I decided to go with minimal changes for now.Here are the error logs for the issue: