-
-
Notifications
You must be signed in to change notification settings - Fork 69
Fix lifecycle handling for signals #57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix lifecycle handling for signals #57
Conversation
Codecov Report
@@ Coverage Diff @@
## master #57 +/- ##
=========================================
- Coverage 19.9% 19.3% -0.61%
=========================================
Files 7 7
Lines 432 430 -2
Branches 74 74
=========================================
- Hits 86 83 -3
- Misses 305 306 +1
Partials 41 41
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Maybe we can add more tests?
|
@evilebottnawi I'm planning to open separate PRs specifically to increase the test coverage and also to refine our architecture! I'll close and merge this for now so we can close the issue and unblock the users 😃 |
|
👍 |
|
Does anyone know when to send a new version containing this pr? @mistic @evilebottnawi |
|
@Dcatfly I believe we are okay to do it early next week 😃 |
|
@mistic let's release new version 👍 |
|
@evilebottnawi @mistic Good~ Thank you for your work~👍😄 |
This PR solves a problem with handling signals on thread-loader process itself which was resulting on process hang in some situations (like for example using webpack-dev-server from a forked process).
Closes #56
\CC @evilebottnawi