change timeout through UP-TIMEOUT header. Closes #814 #815
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
|
awesome thanks! I tweaked it a little, I'll QA and get a release out right away |
|
Just uploading v1.6.0, should be up pretty soon |
|
hmm great it's 100mb haha.. Go mod is really messing things up, I'll look into what's causing the bloat |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See #814
This change allows the timeout to be increased when calling lambda directly while keeping the timeout specified in the config as a default.
The tests run for 50seconds longer now because that's how long the timeout is set, let me know if I should reduce it.