-
-
Notifications
You must be signed in to change notification settings - Fork 803
Open
Labels
area: watcherChanges related to the Taskfile watcher.Changes related to the Taskfile watcher.
Description
Description
Change issued in files elsewhere (not in watch patters) stops watch (issues kill to running command). I do belive this is connected to switch to v[3.43.1](https://github.com/go-task/task/releases/tag/v3.43.1) introduced fsnotify.
part of the log with -v and -w flags
application - 11:06:59 INFO layer=server/http msg=http setup
application - 11:06:59 DEBUG layer=server/http/openapi msg=serving openapi base=/docs spec=/docs/openapi.yaml
application - 11:06:59 INFO msg=[HTTP] server listening on: [::]:8000
task: received watch event: WRITE "/Users/butuzov/Desktop/api.service/scripts/test_api.py"
application - 11:07:13 INFO msg=[HTTP] server stopping
task: "build:live:all" finished
task: task "build:live:all" finished running
task: dynamic variable: "git describe --tags --match 'v*' --always --dirty" result: "dae5ced-dirty"
task: dynamic variable: "git rev-parse HEAD" result: "dae5cedf1460ee7fea4e8bff47c4a703b3e4ef43"
task: dynamic variable: "go env -json | jq -r '.GOOS'" result: "darwin"
task: dynamic variable: "go env -json | jq -r '.GOARCH'" result: "arm64"
task: skipped for file not in sources: scripts/test_api.py
Version
3.48, i did track it back to 3.42.1 as last one not killing current execution, with false signals.
Operating system
macOS
Experiments Enabled
No response
Example Taskfile
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area: watcherChanges related to the Taskfile watcher.Changes related to the Taskfile watcher.