umputun / reproxy / 28693833391

80%

Build Type

push

github

Committed by umputun

Commit Message

Fix file provider dropping config changes made within the delay window

Previously, the debounce compared the file modification time against the
previously submitted modification time, and that baseline only advanced
on submission. A single change landing within file.delay of the last
delivered one kept failing the check on every tick, so the update was
never picked up and routes stayed stale until the file was touched
again.

After this change, the debounce measures stability on the host clock
from when a new modification time is first observed: a change is
delivered once its mtime has held steady for the delay period, and a
newly observed mtime restarts the timer. Rapid writes still coalesce
into a single event, and because a single clock is used throughout it is
immune to filesystem/host clock skew, future- or past-dated mtimes are
debounced normally instead of stalling or bypassing the window (the
earlier wall-clock-age approach delivered future-dated mtimes with no
coalescing on skewed mounts).

The trailing-edge semantics add up to one poll cycle of latency on top
of the delay; the --file.delay help text now describes them. Tests cover
a change within the delay window, rapid writes coalescing, future-dated
writes coalescing on a skewed clock, and a file that appears mid-run
after the loop survives stat errors.

Coverage Stats

16 of 16 new or added lines in 1 file covered. (100.0%)

2 existing lines in 1 file now uncovered.

2644 of 3316 relevant lines covered (79.73%)

40.74 hits per line