No such file or directory, open '/Projects/deep-microservices-image-handler/src/deep-image-handler_lambda_image-handler.zip'
@gcaraman-zz is already working on this.
Since Dec 27, 2017.
Assessment
This issue has not been assessed yet.
Description
$ deepify deploy src
Choose the AWS profile to be used (default/saml): default
Installing latest deep-framework from GitHub
######################################################################## 100.0%
17:22:07 GMT-0500 (EST) Error during compiling:
Prepare for production? (Y/N): y
17:22:11 GMT-0500 (EST) Compilation start
17:22:11 GMT-0500 (EST) Initialize Property instance
17:22:11 GMT-0500 (EST) Ensure shared libraries are globally available (deep-framework)
npm WARN deprecated [email protected]: Use uuid module instead
> [email protected] postinstall /Volumes/Data/Users/eugene/.nvm/versions/node/v6.11.0/lib/node_modules/deep-framework/node_modules/clientjs
> node scripts/install.js
/Volumes/Data/Users/eugene/.nvm/versions/node/v6.11.0/lib
└─┬ [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
└── [email protected] (git://github.com/mishoo/UglifyJS2.git#278577f3cb75e72320564805ee91be63e5f9c806)
17:22:32 GMT-0500 (EST) Extracting lambdas
17:22:32 GMT-0500 (EST) There are no lambdas detected. Skipping...
17:22:38 GMT-0500 (EST) Application resources have been provisioned
17:22:38 GMT-0500 (EST) Make sure you have external lambda zip here
17:22:38 GMT-0500 (EST) Detected external lambda: /Volumes/Data/Users/eugene/Projects/deep-microservices-image-handler/src/deep-image-handler/backend/src/image/handler.zip
17:22:38 GMT-0500 (EST) (node:66024) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): Error: ENOENT: no such file or directory, open '/Volumes/Data/Users/eugene/Projects/deep-microservices-image-handler/src/deep-image-handler_lambda_image-handler.zip'
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MitocGroup/deep-microservices-image-handler
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 20/100
All issues in MitocGroup/deep-microservices-image-handler
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
521xueweihan/HelloGitHub#4073 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
c1overzz/dsh-bili-scroll#79 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
awesome-dsh-plugin/awesome-dsh-plugin#8715 ·
Maintainers usually reply within 1 day