Use certifi certs for buck download #10095
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Depending on how Python is installed and managed, it is common for certificates to not be installed out of box on Macs. This can cause the download of buck2 as part of the build process to fail with a certificate error.
While the ultimate solution for this is for the user to install certs in their environment, we can smooth this over a bit for build by pointing urllib at the certifi package certs, which we install as part of install_requirements.
Test plan
I worked with @nil-is-all to verify that this fix allowed him to build and install ExecuTorch from a clean environment. Without this change, he was seeing cert failure errors during buck download.