aws / aws/chalice

chalice deploy didn't finish apparently because of big resulting package

Open
#1,727 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
11.1k
Forks
1k
Avg merge
1d 22h
Merged PRs (30d)
2

Description

I have a local setup that uses `xgboost==0.90`, the `chalice deploy` command does not finish successfully (does not finish at all).

I tried with vanilla inclusion in requirements.txt and It gave me `PackageDownloadError`.

I also tried packaging manually the library at the `vendors/` folder but when running `chalice deploy` again it gets Killed after an 'updating Lambda instance' message; It seems that in a given test it uploaded the code but incomplete, given that the deployed API was not indexed in deployed, and when tested the URL provide for API gateway it didn't install a library that was included in the `requirements.txt`.

I think that the problems have to do with the size of the `xgboost` package (~156mb) but not sure.

I understand that keeping the size of packages deployments small is a good practice but I wonder if this specific case can have a solution.

Thanks in advance, and thanks for this project :raised_hands:

Contributor guide

Open the contributing guide

Research direction

Start by reproducing `chalice deploy` with `xgboost==0.90` in `requirements.txt`, then compare it with the manual `vendors/` packaging described in the issue. Check the resulting `PackageDownloadError`, the “updating Lambda instance” step, and whether the deployed API and dependency are present; done should be a clear diagnosis or documented handling for this package-size case.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, python
Domain
backend, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.