-
Notifications
You must be signed in to change notification settings - Fork 130
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
Change windowsHide to false #876
Conversation
Thanks for your contribution! Depending on what you are working on, you may want to request a review from a Shopify team:
|
@@ -68,6 +68,7 @@ const buildExec = (command: string, args: string[], options?: ExecOptions): Exec | |||
stdin: options?.stdin, |
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.
I'd adjust this one to options?.stdin ?? 'inherited'
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.
I tried this, but running dev
quits unexpectedly after showing the logs. I suspect there is some issue with the ruby executable being run with this. Perhaps something for another PR?
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.
Tophatted and works as expected. Brilliant finding here @matteodepalo
eba2aca
to
ca8141b
Compare
Coverage report
Test suite run success417 tests passing in 238 suites. Report generated by 🧪jest coverage report action from ca8141b |
WHY are these changes introduced?
Fixes #630
On Windows, processes are left hanging around after users terminate
dev
withCtrl+C
. Digging around I found an issue open on theexeca
repo that mentioned issues withSIGINT
and child processes not getting killed properly on Windows ifwindowsHide
is left to its default value oftrue
.WHAT is this pull request doing?
This PR changes the value of
windowsHide
from its default oftrue
tofalse
. This did not seem to have any effect on the behavior ofdev
How to test your changes?
yarn shopify app dev --path fixtures/app
on WindowsCtrl+C
and see all the node processes disappear.There will be 1 node process remaining, but this behavior also happens on Mac and there we haven't had any problems with cleaning up child processes. If that single process becomes a problem we can investigate further, but for now this change should make the two platforms behave the same.
Measuring impact
How do we know this change was effective? Please choose one:
Checklist
dev
ordeploy
have been reflected in the internal flowchart.