Fix #490: Connection timed out after 120000ms in function deployment #937
Conversation
This file contains hidden or 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
|
is There example for how to do it? because i didnt understand how to export it... |
Contributor
Author
|
I haven't used this in years, but I expect ... For further support let's move the conversation over to the forums. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This allows users to work around a network with a slow upload speed by setting the
AWS_CLIENT_TIMEOUTenvironment variable to something greater than 120000 (2 minutes). If found, it sets theAWS.client.httpOptions.timeoutvalue.It follows the existing convention set by looking for
HTTP_PROXY/HTTPS_PROXYin the environment.