-
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
Build failing - Error in ResolveDependencies for fastparquet #3553
Comments
What Lambda architecture are you using? Also see potentially related #1840. I ran the following: sam init --name sam-app --runtime python3.9 --dependency-manager pip --app-template hello-world
cd sam-app
echo 'fastparquet==0.6.3' > hello_world/requirements.txt
sam build --use-container --debug Which succeeds:
|
@hoffa x86_64 architecture |
In that case the comment above still applies; I'm unable to reproduce with the steps you provided: sam init --name sam-app --runtime python3.9 --dependency-manager pip --app-template hello-world
cd sam-app
echo 'fastparquet==0.6.3' > hello_world/requirements.txt
sam build --use-container --template ./template.yaml --debug Builds fine. Can you confirm that running the commands above work? One difference I'm seeing is that you're using SAM CLI 1.28.0, while mine is 1.36.0. If the above steps don't work, you might want to try updating SAM CLI first. |
@Monal5031 can you please confirm if your issue is resolved by latest version of aws-sam-cli? |
Hey, Yes I tried with the latest version of aws-sam-cli and it works with it. Due to dependency in other packages it won't be possible for us to use the latest version. Is there any workaround that's possible? Thanks for help 😄 |
Thanks for confirming @Monal5031, I was able to reproduce your issue with latest version as well, actually it is not an issue with sam-cli but fastparquet's wheels. I would still recommend using latest version of sam-cli and would like to know more about the constraints where you are not able to use latest version of sam-cli. Long explanation:
Notice that pip was also not able to find the required wheels and went ahead with building the dependency on local. This is because fastparquet's provide wheels only upto macos 10.9. I am not 100% sure why sam-cli's use of pip don't actually build the dependency but one reason can be security. When you use |
Actually I looked more into this issue and it looks like an issue with how sam-cli triggers pip installation. After adding some logs to lambda-builders I see following lines before attempt to build fastparquet wheel fails:
When try to install using pip, it also tries to build the wheel and the same command is below:
On looking closely |
Hey @c2tarun, Thanks a lot for looking into it. |
Glad to hear that issue is fixed on your side @Monal5031 If you are installing SAM CLI through pip, we recommend using a separate virtual environment for that, for not facing any issues with dependency resolution. Please comment or create a new issue, if you are still facing this or similar problem. |
Description:
I have a piece of code which works with
fastparquet==0.6.3
and python 3.9 locally and when I try to deploy it to AWS lambda via aws-sam-cli, the build fails.Steps to reproduce:
fastparquet==0.6.3
as part of requirementsam build --use-container --template ./template.yaml
Observed result:
Expected result:
Successful build.
Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
sam --version
: 1.28.0Add --debug flag to command you are running
The text was updated successfully, but these errors were encountered: