Allow overriding init timeout via parameters #206
Merged
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
…r than environment variable
|
Hey @haggholm, that makes sense! Thanks for the contribution 👍 |
|
Published as v1.1.0 🚀 |
kellyselden
added a commit
to kellyselden/threads.js
that referenced
this pull request
Oct 8, 2020
I spent half the day scratching my head on this one. I searched your repo for "docker" and found [this issue](andywer#206), which solved it. I would like to make it easier for others to find this solution.
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.
We have some environments (involving Docker containers or Webpack builds, &c., &c.) where (a) setting the timeout via env var is awkward, and (b) some development machines experience timeouts. It would be nice to be able to override the default timeout via parameters.