peach-android / 453bcdaba9ef

fix: dialer takes 60s cooldown after clean-complete close (v2.9.17) After a clean 'relay session complete' the dialer was re-dialing the same target at the 5_000ms reconcile cadence, burning a full 20s ping/pong timeout per cycle. Reproduced live: 00:10:16.688 clean close -> 00:10:21.691 redial -> 00:11:08.408 timeout. Visible in logcat as the third/fourth dial attempts after a successful sync. - New constant DIAL_CLEAN_COMPLETE_COOLDOWN_MS=60_000L (private), used only by the new early-return in nextRelayRetryDelay. - nextRelayRetryDelay: succeed+dialer now returns the long cooldown instead of resetting to DIAL_RETRY_DELAY_MS. Waiter success and failed-dialer paths unchanged. Minimum diff, single line of new branch logic. - Existing test renamed and updated to pin the new behavior: succeeded+dialer pins 60_000L, not 5_000L. The spec test 'clean-complete dial ramps the dialer cooldown above the reconcile hot loop' (added in v2.9.16) flips from intentionally red to green as the executable spec for this fix. CONTINUITY.md updated; checkpoint ce204bae8990 is the pre-edit restore point. Gate: testDebugUnitTest --tests com.peachpasswords.sync.* --rerun-tasks — 37 sync classes, 0 failures, 0 errors. Full sync package clean.

dev · 4 weeks ago · 2026-07-31 · 5.7 MB

parent: ce204bae8990