watchmedo only triggers once (and sometimes not even once)

[cglacet]

I have a problem I can't manage to identify, I'm not sure it's a bug with watchmedo command tho.

When I run the following:

poetry run watchmedo shell-command \
    --patterns='*.rst;*.py' \
    --ignore-pattern='public/*' \
    --command='echo test' \
    --recursive

Everything works as expected and any change triggers the echo command, on the other hand, if I change echo test by poetry run python -m sphinx -a -E -b html source public (which on its own work without any issue, ie., error code is 0) I get strange behaviours.

Most of the time the first change triggers documentation build as expected. Subsequent changes will never trigger and the command build will not be executed anymore.

Any clue what could be causing this?

EDIT I also test with this command poetry run python -m sphinx -a -E -b html source public && echo status $? just to make sure everything went well even when started from the first auto-trigger. And it also printed status 0.

2nd EDIT I found a command you can try at home and produces similar (unexpected) results:

❯ poetry run watchmedo shell-command \
                --patterns='*.rst;*.py' \
                --ignore-pattern='public/*' \
                --command='echo test && sleep 10 && echo ok' \
                --recursive

After the first edit, this should print test \n ok then it will stop triggering after subsequent edits.

3rd EDIT using --debug-force-polling seems to prevent this bug from appearing (both in the sphinx build and sleep 10 cases), no idea what that does 🤣

[CCP-Aporia]

Which operating system are you running on? :-)

[cglacet]

Osx, catalina I think is the name. If you need more details I can check once I'm back on my laptop.

[CCP-Aporia]

Great, thanks! Then the problem is most likely with the fsevents based observer that is the default on macOS. You could also try using the kqueue based observer (--debug-force-kqueue) which should perform better than the polling one.

[josemonsalve2]

Hello,

I am having the same issue, but when using the python module. Is there a way to force kqueue in python?

Thanks

[samschott]

I think this can be closed following the release of 2.0.