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

Lambda Size Limit 6MB #39

Closed
jonsharratt opened this issue Feb 13, 2017 · 1 comment
Closed

Lambda Size Limit 6MB #39

jonsharratt opened this issue Feb 13, 2017 · 1 comment
Assignees
Labels

Comments

@jonsharratt
Copy link
Member

jonsharratt commented Feb 13, 2017

Bug Report

Seems because the attachements are stored it quite quickly hits the 6MB limit when requesting files from S3.

Description

For bug reports:

  • What went wrong?
    body size is too long is too long from Lambda in get.js

  • What did you expect should have happened?
    Relevant private package should be returned

  • What was the config / env variables you used?
    N/A

  • What stacktrace or error message did you
    experience?
    body size is too long

Additional Data

  • NPM CLI version you are using:
    3.10.10
  • Serverless version you're using:
    1.5.1
  • Node version you're using:
    6.9.5
  • Yith Version:
    0.7.0
@jonsharratt jonsharratt self-assigned this Feb 13, 2017
@jonsharratt
Copy link
Member Author

Proposed fix is not to store / return the attachements within the index.json file as looking at https://registry.npmjs.org/react as an example attachments are not returned. Makes sense thinking about it as longer term that would be an unmaintainable response size.

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

No branches or pull requests

1 participant