You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed that Task kills the process when reloading it in Watch mode instead of gracefully terminating it with SIGTERM:
As far as I can tell, this happens because the task context gets cancelled here, which seems to just kill the process instead of sending an interrupt signal.
It would be nice if there was an option to gracefully stop it instead (and wait for it to stop, in case the cleanup takes a while).
I think it should also behave like InterceptInterruptSignals and forcefully exit if 3 consecutive interrupts are detected (in case shutdown hangs).
My machine is running Windows 10 by the way.
The text was updated successfully, but these errors were encountered:
it seems when I run only "go run main.go", it's not closing the process, and running multiples times when I change files. I tried to run only build of go and run it, it seems that has working well
@andreynering I'm assuming this change would be required to support properly sigterming a go run server.go process where it boots up a web server which binds to a port, thus needing to be cleaning killed?
I've noticed that Task kills the process when reloading it in Watch mode instead of gracefully terminating it with SIGTERM:
As far as I can tell, this happens because the task context gets cancelled here, which seems to just kill the process instead of sending an interrupt signal.
It would be nice if there was an option to gracefully stop it instead (and wait for it to stop, in case the cleanup takes a while).
I think it should also behave like
InterceptInterruptSignals
and forcefully exit if 3 consecutive interrupts are detected (in case shutdown hangs).My machine is running Windows 10 by the way.
The text was updated successfully, but these errors were encountered: