-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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(core): allow isolated plugins to shut themselves down #27317
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
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.
Verify that this fixes the windows issue and then, re-enable isolation on Windows in this PR
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 5e43458. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 4 targets
Sent with 💌 from NxCloud. |
Works on my windows machine :) |
1603151
to
5e43458
Compare
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Current Behavior
Isolated plugin workers are shutdown via
childProcess.kill()
in aprocess.on('exit)
handler.Expected Behavior
Isolated plugin workers are shutdown via a message sent over their socket, which tells the to clean themselves up
Related Issue(s)
Fixes #