Closed moryachok closed 6 months ago
Thanks for raising this issue. I can reproduce the issue where it is stuck building the project. It is actually doing something, however that isn't being streamed back to terminal while the container runs. It looks like pip is having problems trying to resolve the dependencies between glue
and s3fs
.
It looks like the glue
extra installs botocore==1.34.80
:
botocore==1.34.80
# via
# boto3
# s3transfer
While s3fs
will install botocore==1.34.51
:
botocore==1.34.51
# via aiobotocore
Both of these were installed separately in their own venv, and pip-compile
was used to list the installed child dependencies.
pip
is trying to download and compare every single dependency between them to find something that works.
It looks like https://github.com/apache/iceberg-python/pull/534 in the iceberg repository fixes most of the issues with dependency resolution when I pulled it down to quickly test. Can you check in with the folks over there just to confirm?
As a workaround for now, you can pin boto3
and botocore
just before installing pyiceberg
, like this:
boto3==1.34.51
botocore==1.34.51
pyiceberg[s3fs,glue]
Hey @lucashuy, your workaround worked for me, thanks for deep dive.
Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.
Description:
sam cli build --use-container
stuck when I use extras install in requirements txt.Examples of requirements.txt:
pyiceberg[s3fs,glue]
- stuckpyiceberg[s3fs]
- workspyiceberg[glue]
- worksSteps to reproduce:
add
pyiceberg[s3fs,glue]
to yourrequirements.txt
and run buildObserved result:
Expected result:
build finish successfully
Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
sam --version
: reproduced on versions 1.78.0 and 1.114.0