watch inside of docker runs multiple times

[fnivek]

Description

Running a task with watch inside a docker container runs multiple times at the same time.

I have a task like:

  watch:
    desc: Continually run ci on ever change.
    watch: true
    sources:
      - src/**/*
    cmds:
      - clear
      - do ci

If it is run in the container I expect it to run just once per change, however; it runs multiple times ever time a file in src is changed. Presumably due to how docker mounts and edits file shared file systems. When I run outside of the container it works as expected. For now my workaround is this:

  watch:
    desc: Continually run ci on ever change.
    watch: true
    sources:
      - src/**/*
    cmds:
      - clear
      - task: env:enter-dev-container
        vars: { DOCKER_ENTRY_CMD: 'task ros:ci'}

Inside docker:

$ task --version 
3.43.3+pypi

Outside docker:

$ task --version
Task version: 3.41.0 ()

Version

3.43.3+pypi

Operating system

Linux d50ea3e7f517 6.5.0-35-generic #35~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue May 7 09:00:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

Experiments Enabled

No response

Example Taskfile

version: '3'
tasks:
  watch:
    desc: Continually run ci on ever change.
    watch: true
    sources:
      - src/**/*
    cmds:
      - clear
      - do ci

[timrulebosch]

@fnivek You are probably correct. Try adjusting the interval for the watch (see doc), so its less sensitive to the speed/rate of underlying file-system changes..

[tboerger]

It's not related to Docker, looks like it is related to recent versions of go-task as this also happens to me within a devenv/nix environment where I got an updated version since today.

Edit: 3.41.x worked perfectly fine related to that, 3.43.x tries to launch watched processes multiple times.

[fnivek]

Oh I did start my docker container from within a nix shell, I didn’t think that would matter and my local machine is also in a nix shell but that worked. My colleague also had the same issue and he was just in a docker container nix wasn’t even installed on his machine. To be precise I use direnv with use_flake To bring in my dev environment I can share that setup if it would help.
Also I will play around with the interval and see if that helps.

[tboerger]

The latest go-task version on nixpks unstable is also affected.

[fnivek]

Adjusting the interval doesn't seem to change the number of times the watched task is executed. I tried 5000ms and 10s neither changed the behavior.

[tboerger]

Yeah I can confirm that, for me it's the same behavior for various intervals

[DeCorben]

I just ran into this is problem (macOS, no docker) and noticed that the number of parallel process it runs seems to correlate with the number of array entries in the task's sources property.

[andreynering]

I just opened a PR with some fixes to the recent regression:

• fix(watcher): fix some v3.43.x regressions #2271

Do you mind testing the letting me know if it improves the situation?

[andreynering]

Closing after #2271. I'm open to opening this again if there is any feedback that this still isn't working correctly.