Repository navigation
aw-sync: daemon pull is opt-in (default off) for v0.14.0b8 — first config.toml in the aw-sync config dir #714
Description
Activity
Shipped: #716
Adds
config.tomlin aw-sync's own config dir ({config}/activitywatch/aw-sync/, profile-aware — thetestingprofile gets its own file), default-commentedpull = false. Daemon reads it once at startup:pull=false->SyncMode::Push,pull=true->SyncMode::Both; an explicit--modestill overrides either way.aw-sync sync(one-shot) is unaffected.aw-sync statusnow prints the effective mode and the config path it read.The #687 "zero peers" warning suppression came for free —
sync_run()only captures those discovery warnings whenmodeisPull/Both, so a push-only daemon pass produces none without extra gating.Verified end-to-end against a scratch
XDG_CONFIG_HOME(file gets created with the commented default on first run;pull = trueflips the daemon toboth). All 53 aw-sync tests pass, plus 4 new ones for the config load/create and effective-mode logic. CI is running on the PR now.- added a commit that references this issue
on Sep 18, 2026 @0xbrayo Agreed — verified against current master, not just the merge.
#716 (
70ba50dd) is an ancestor of master. The #714 checklist still holds:- daemon pull is one setting in aw-sync's own profile-aware config (
{config}/activitywatch/aw-sync/config.toml, namespaced as[daemon].pullafter Erik's review) - missing file is created with the commented
pull = falsedefault on first daemon start;aw-sync statusis read-only and does not create it - no
--mode+pull=false→SyncMode::Push;pull=true→Both; explicit--modewins and skips config load - one-shot
aw-sync syncis untouched statusprints the config-derived mode and path; push-only passes do not emit the feat(aw-sync): addstatusdoctor command and fail-loud empty-pull warnings #687 pull-discovery warnings
I don't have CloseIssue on ActivityWatch/aw-server-rust (403). @ErikBjare please close this as completed — the remaining follow-on from ActivityWatch/activitywatch#1445 is sync v2 (manifest + segment writer), not this issue.
- daemon pull is one setting in aw-sync's own profile-aware config (
Decision by Erik for v0.14.0b8: with #710 merged the daemon can pull, but it must not pull by default. 0.14 is push-only everywhere unless the user opts in — Android by design (ActivityWatch/aw-android#291), desktop because #711 (boundary re-import every pass) is unfixed and because sync v2 will replace pull with "read from the sync folder". Erik opts in on his own machine to test sync v1, the multidevice query, etc.
Requirement
dirs::get_config_dir()already exists ({config}/activitywatch/aw-sync/, profile-aware, "TODO: add proper config support") — add the firstconfig.tomlthere, e.g.SyncMode::Push);pull = true⇒SyncMode::Both. An explicit--modeon the command line still wins.aw-sync sync(the one-shot) is unaffected — it stays pull+push, that is how testers verify an import.aw-sync statusprints the effective mode and where the config was read from, and the feat(aw-sync): addstatusdoctor command and fail-loud empty-pull warnings #687 "zero peers … layout problem" warning is suppressed when pull is off (there was no pull).Tests: daemon pass with no config ⇒ Push; with
pull = true⇒ Both;--mode pulloverrides apull = falseconfig.Sequence agreed on ActivityWatch/activitywatch#1445: #712 → this → #711 → v2 (manifest + segment writer). The default flips when #711 is fixed, or is superseded by v2's read-from-staging.
cc @TimeToBuildBob