You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using git-sync and fava with docker-compose to share the ledger with my partner.
git-sync "publishes" each sync through a worktree and a named symlink to ensure an atomic update.
The problem is that when I update and push the ledger for the first time after the fava docker runs, fava can catch changes. But when I update and push the ledger again, fava cannot catch changes.
This means in my situation, fava can only catch changes for the first time.
I checked the code. Maybe the cause is fava only watches the absolute path of files.
I'm using git-sync and fava with docker-compose to share the ledger with my partner.
git-sync "publishes" each sync through a worktree and a named symlink to ensure an atomic update.
The problem is that when I update and push the ledger for the first time after the fava docker runs, fava can catch changes. But when I update and push the ledger again, fava cannot catch changes.
This means in my situation, fava can only catch changes for the first time.
I checked the code. Maybe the cause is fava only watches the absolute path of files.
fava/src/fava/core/watcher.py
Lines 147 to 148 in e71d724
BTW, I tried
--poll-watcher
option. It works.The text was updated successfully, but these errors were encountered: