-
-
Notifications
You must be signed in to change notification settings - Fork 229
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
Add feature to retry process killing after specified duration #208
Add feature to retry process killing after specified duration #208
Conversation
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 for this PR @zokker13.
Sorry for the verbosity of the review!
Also at the end, don't forget to:
- add tests.
- make sure CI is passing.
- update the documentation.
Thanks!
@ehmicky Thanks or the review. I implemented some changes, feel free to check them out again. |
Looks good to me! We need a review from @sindresorhus as well. I added two minor suggestions. It does not look like CI has failed, so all good there :) Thanks for this PR again! 🎉 🎉 🎉 |
@zokker13 thanks for this new batches of updates! Hopefully we can merge this soon! 🎉 🎉 |
@ehmicky Ready for another attempt ^^ |
Thanks! I think I figured out the problem with your test, see my comment. Also I added a suggestion for another test. And there are some linting issue with the fixture file. Thanks for holding on :) |
Thanks for finding that detail! I'm ready for anothr go :) |
The tests are failing on CI for Windows. From looking at the commit history, it started failing on Windows after adding the |
I think the ipc change is just the bad messenger since the tests never truly reported what's really there. I'll make a quick cross check with normal stdout as trigger tomorrow evening. |
`retry` => `forceKill` `retryAfter` => `forceKillAfter`
ca5532c
to
756cb78
Compare
@ehmicky wow, I was finally able to rebase master in here so you may check it out again. |
Rebase looks good :) |
@ehmicky what else is needed to have it merged? |
Looks good now :) |
Thanks a lot @zokker13! I hope the code review process was not too tedious for you! |
It was okay. I didn't expect so much back and forth but that means people care for the package/feature so it's a good thing :) |
Yes This feature is great, thanks a lot for the effort put into it! |
Ya, the usage is pretty overwhelming. |
Hi,
this PR fixes #105.
I'm wondering if the approach is good. If so, I'll add tests.
Personally, I'm not sure about the options parameter. It seems odd to be forced pass a parameter for the timeout but at the same time it's fine since there's a default value in the code.