Skip to content
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

502 bad gateway when npm install #16

Closed
MrHertal opened this issue Jun 10, 2020 · 2 comments
Closed

502 bad gateway when npm install #16

MrHertal opened this issue Jun 10, 2020 · 2 comments

Comments

@MrHertal
Copy link

Hi, thank you for this very useful project.
I was able to make it work perfectly, but now I have an error when running:

npm install 'https://gitpkg.now.sh/MrHertal/amplify-cli?react-admin-amplify&scripts.postinstall=npm%20install%20--ignore-scripts%20%26%26%20npm%20run%20build%20%26%26%20npm%20prune%20--production'

Which gives me:

npm ERR! code E502
npm ERR! 502 Bad Gateway - GET https://gitpkg.now.sh/MrHertal/amplify-cli?react-admin-amplify=&scripts.postinstall=npm%20install%20--ignore-scripts%20%26%26%20npm%20run%20build%20%26%26%20npm%20prune%20--production

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/ghertault/.npm/_logs/2020-06-10T10_16_01_143Z-debug.log

I think that what causes the issue is that the repository https://github.com/MrHertal/amplify-cli is a fork that I deleted (for personal reason) then recreated again. Since I did that, it does not work anymore.

Thank you for your help.

@MrHertal
Copy link
Author

Sorry I made a dumb mistake,

I forgot to include subfolder in the repo url:

npm install 'https://gitpkg.now.sh/MrHertal/amplify-cli/packages/amplify-graphql-docs-generator?react-admin-amplify&scripts.postinstall=npm%20install%20--ignore-scripts%20%26%26%20npm%20run%20build%20%26%26%20npm%20prune%20--production'

Now it is working.

@EqualMa
Copy link
Owner

EqualMa commented Jun 10, 2020

Thanks for pointing this out, I'm glad that you make it work. But the link without subfolder should also work.

As reported in the logs, the error is LAMBDA_RUNTIME Failed to post handler success response. Http response code: 413.

I searched about this error message, and I found this is because of the limitation of aws lambda (vercel now is on it), as talked in this issue. The invocation payload maximum limit is 6MB. Thus, if the repo is very large, the file size exceeds 6MB, then the request will fail.

I don't know how to overcome this limitation, ideas are welcome~

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants