-
Notifications
You must be signed in to change notification settings - Fork 210
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
Node process not stopped #143
Comments
@srs Are you still interested in maintaining this plugin? |
I noticed someone had a similar problem and fixed it on a fork: laurimak@2505514 |
Hi. Yes, still maintaining it since I use it in a lot of projects. It would be great to have a pull-request of this fix ;-) |
@srs The code seems to have changed significantly since that fork was made. Could you take a look and attempt to apply it? |
Yes, will do. |
I have the same issues while running angular-cli via YarnTask from gradle After killing gradle with CTRL+C angular-cli is still running |
I've found temporary solution. Disabling gradle deamon fix this issue. Just create following gradle.properties file in project directory
With deamon disabled everything works allright. |
hi @kucharzyk, seems your solution doesn't work to me, I use gradle to start webpack-dev-server, after stop the gradle task in Intellij, the webpack-dev-server is still working. |
I have the same problem... A solution would be very great @srs :/ |
I was having the same issue from a create-react-app project when trying to run the webpack dev server through yarn.
What I saw was gradle would start a yarn process using project.exec and yarn would then start a node process (node script/start.js). When Gradle exited, the yarn process would exit, but the subsequent node process would stay around. I worked around this by just calling node directly using
Now gradle only spawns a single node process and when gradle exits the node process exits (after a handful of seconds). This is certainly still an issue, but I've found this to be a very acceptable work around. |
Adding
|
alternatively you can still use the the deamon but use |
Tried different Gradle version. I'm having this issue with Gradle 3.2 and later (including 4.7, which is latest). Probably related to Ctrl-C changes described here: https://docs.gradle.org/3.2/release-notes.html#ctrl-c-no-longer-stops-the-daemon-on-first-run Using My build.gradle:
|
I've configured a task to start a server to serve static assets:
When I stop the gradle task, the node executable keeps running. What are my options to ensure the process gets shut down?
The text was updated successfully, but these errors were encountered: