Signal option for watched mode (instead of just killing the process)

[HeCorr]

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.

[larry868]

Same requirement for me, on ubuntu,

# launch it with --watch 
  live_back:
    dir: '{{.USER_WORKING_DIR}}'
    sources:
      - "./pkg/**/*"
      - "./cmd/**/*"
    cmds:
      - go run ./cmd/hellogoapp/main.go

In my case the task is a http server, killing the process does not free up the http port.

My current option: I use task to run air :-(

[HeCorr]

Go 1.20 has new methods in the Cmd struct that allow this behavior to be configured: Cancel and WaitDelay.

[vinicius73]

Same here

[vitorvargasdev]

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

why its work? I don't know, but's it work :)

version: '3'

tasks:
  default:
    cmds: [
      'go build main.go',
      './main'
    ]
    sources: [
      ./*.go,
      ./**/*.go
    ]

[danawoodman]

@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?