Skip to content
This repository has been archived by the owner on Apr 20, 2019. It is now read-only.

fix: closes all connections when stopped #41

Merged
merged 2 commits into from
Nov 12, 2018
Merged

Conversation

jaulz
Copy link
Contributor

@jaulz jaulz commented Nov 11, 2018

This fix closes all connections when the Hapi server is stopped. Otherwise the node process will continue running until the last connection was closed.

This fix closes all connections when the Hapi server is stopped. Otherwise the node process will continue running until the last connection was closed.
Copy link
Contributor

@Nargonath Nargonath left a comment

Choose a reason for hiding this comment

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

The travis ci build failed. Please check travis log there are some code format issues (missing semi-colons and so on) plus you'll need to add some tests to cover the new code you added. The coverage was at 100% on last build and usually there is a 100% coverage on all module in HapiJS org.

@jaulz
Copy link
Contributor Author

jaulz commented Nov 11, 2018

Yep, will tackle this tomorrow. Just wanted to get a feeling first if any PR is welcome since the latest welcome is quite old 😊

@Nargonath
Copy link
Contributor

Thanks for your contribution. PR are always welcomed 😉. However I'm not the lead maintainer on this project. I intervened because there were some more work required to make the PR mergeable but in the end @geek will have the final word when it comes to accept or not the contribution.

@jaulz jaulz force-pushed the patch-1 branch 5 times, most recently from e52cbf2 to 055e0f5 Compare November 12, 2018 13:26
@jaulz
Copy link
Contributor Author

jaulz commented Nov 12, 2018

@Nargonath @geek I created tests for the new feature but in Node.js v11 some strange things happen with the experimental microtask queue. any idea how we could fix this or if we can ignore this in the meantime?

@Nargonath
Copy link
Contributor

I think there is a problem with Node 11 at the moment. Perhaps @geek just need to disable the Node 11 job for now as it's been done in hapijs/nes#257.

Copy link
Contributor

@Nargonath Nargonath left a comment

Choose a reason for hiding this comment

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

I approve the PR based on my previous review because code is now 100% coverage and lint errors have been fixed however someone with more knowledge of the project should have a look at the feature itself.

@jaulz
Copy link
Contributor Author

jaulz commented Nov 12, 2018

Great, thanks! Looking forward for @geek feedback 😊

@geek geek added the bug label Nov 12, 2018
@geek geek self-assigned this Nov 12, 2018
@geek geek added this to the 3.0.1 milestone Nov 12, 2018
@geek
Copy link
Contributor

geek commented Nov 12, 2018

@jaulz I'll update master to use different node versions on travis. Thanks for the fix.

@geek geek merged commit 5154e76 into outmoded:master Nov 12, 2018
@geek geek modified the milestones: 3.0.1, 3.0.2 Nov 12, 2018
@jaulz jaulz deleted the patch-1 branch November 12, 2018 19:32
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants