--file-watch and --exec with running server like command does not build again

[ecthiender]

General summary

If you run any command via the --exec flag which does not exit (like a server), then --file-watch does not build again if the files changes.

I can understand why that is, and it is probably how the implementation is - but it is counter-intuitive.
Other dev tools (like gunicorn, go's reflex) works as expected. If a file changes, even with server like commands, it rebuilds/reloads and runs the commands again.

Steps to reproduce

stack build --fast --exec "sleep infinity" --file-watch

2. Change a file in the same project

Expected

The build happens again, and the exec command is run again.

Actual

Nothing happens. (Because the exec command never exited)

Stack version

$ stack --version
Version 1.7.1, Git revision 681c800873816c022739ca7ed14755e85a579565 (5807 commits) x86_64 hpack-0.28.2

Method of installation

• Official binary, downloaded from stackage.org or fpcomplete's package repository

---

PS: There is an issue #2955 . But that is different than this issue.

[mattaudesse]

Seems like a nice enhancement and also more intuitive - thanks for the suggestion @ecthiender .

Is this something you'd like to try and implement?

[ecthiender]

Sure, why not!

[vlatkoB]

Maybe something like stack run --file-watch? That was the first thing I tried, similar to stack test --file-watch.

[qcc-na]

@ecthiender You wouldn't happen to have a update on this would you?

[DoctypeRosenthal]

[m4lvin]

Issue #1765 is related and there the following workaround was given by @5outh:

$ stack build --file-watch --exec "bash -c \"pkill my-api; stack exec my-api &\""