fix(Shard): use provided timeout when respawning #6735
Merged
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.
Please describe the changes this PR makes and why it should be merged:
This PR resolves #6575 in a semver: patch manner by attaching the provided timeout to the exit listener which then passes this timeout back to the spawn method.
Also resolved a bug where
Shard#spawn
would not return a promise when the timeout was disabled.A semver: major solution would be to remove timeout parameters and make them properties to be specified when constructing the sharding manger (or at least the shard).
Status and versioning classification: