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

Scale the lambda_timeout parameter correctly. #579

Merged
merged 1 commit into from
Nov 16, 2017

Conversation

ttung
Copy link
Contributor

@ttung ttung commented Oct 25, 2017

lambda_timeout in the config is in seconds, but LambdaContext wants the timeout in ms.

lambda_timeout in the config is in seconds, but LambdaContext wants the timeout in ms.
@codecov-io
Copy link

codecov-io commented Oct 25, 2017

Codecov Report

Merging #579 into master will increase coverage by <.01%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #579      +/-   ##
==========================================
+ Coverage   94.65%   94.66%   +<.01%     
==========================================
  Files          18       18              
  Lines        3164     3167       +3     
  Branches      412      413       +1     
==========================================
+ Hits         2995     2998       +3     
  Misses        118      118              
  Partials       51       51
Impacted Files Coverage Δ
chalice/local.py 98.28% <100%> (+0.01%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 91ff9d2...934a6ca. Read the comment docs.

Copy link
Member

@jamesls jamesls left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the pull request!

@jamesls jamesls merged commit 3503c2e into aws:master Nov 16, 2017
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

Successfully merging this pull request may close these issues.

3 participants