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

Max Memory In "Publish To AWS Lambda" Wizard Is "3008" #362

Open
mjh-mshiker opened this issue Sep 13, 2023 · 1 comment
Open

Max Memory In "Publish To AWS Lambda" Wizard Is "3008" #362

mjh-mshiker opened this issue Sep 13, 2023 · 1 comment
Labels
bug We can reproduce the issue and confirmed it is a bug.

Comments

@mjh-mshiker
Copy link

Describe the bug
When attempting to publish an AWS Lambda using the wizard, the max memory value in the drop down list is 3008 so I cannot publish for a desired memory value of 4096. For a Lambda which is already published and configured in AWS for 4096, when I attempt to re-publish, the value of 4096 is not read in and the drop down list does not have any value selected. If I try to publish without a memory value selected, the extension crashes.

To Reproduce

  1. Right click an AWS Lambda project and choose Publish to AWS Lambda...
  2. Try to select a value for Memory greater than 3008

Expected behavior
The drop down values should include values from 128 to 10240 as indicated by this statement on the AWS Lambda General configuration view in the webpage in the AWS webapp "Set memory to between 128 MB and 10240 MB".

Screenshots
20230913-105121
20230913-105150

Computer (please complete the following information):

  • Windows Version: 11
  • Visual Studio Version: 17.4.5
  • AWS Toolkit for Visual Studio Version: 1.43.0.0

Additional context
I am also attaching a screenshot of the info tip that is displayed when I hover the Memory drop down list. It incorrectly states that increments can only go to a max of 1024. That is less than the 3008 which is in the drop down and less than 10240 actual. Maybe it is just missing a trailing "0" for the 10240.

@mjh-mshiker mjh-mshiker added the bug We can reproduce the issue and confirmed it is a bug. label Sep 13, 2023
@shruti0085
Copy link
Contributor

Thank you for bringing this issue to our attention. We are investigating further.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug We can reproduce the issue and confirmed it is a bug.
Projects
None yet
Development

No branches or pull requests

2 participants