What
The background worker that syncs a directory over git no longer treats a failure as one general offline state. It now counts failures on its journal lane and its object lane independently, so a stale journal is logged and surfaced as its own condition, and it takes a new wait-before-proceeding duration that applies to whichever lane is down.
Details
- The offline signal is reported per lane, with the journal lane named specifically when it is the stale one, instead of a single shared counter covering both.
- A configurable duration, internally
laneDownProceedMs, sets how long the worker waits before proceeding while a lane is down. - Applies to cloud and self-hosted sessions that use directory sync.
Evidence
dir_sync_git_worker_offline, laneDownProceedMs
Strings lifted out of the shipped bundle, so the claim above can be checked against them.