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
Fix bug #7: serialize forward retries in their own background loop
retryPendingForwards was forked every 30s from backgroundPrune with no
in-flight guard, so a slow run (many peers/forwards, slow fetches) would
overlap with the next tick. Parallel runs see the same *forwards
snapshot, attempt the same fetches, and double-count recordFailure on
shared failures — inflating the per-peer backoff multiplier.
Split retry into its own backgroundRetryForwards loop that calls
retryPendingForwards inline (no fork) so a slow run delays the next
iteration instead of racing with it. Gated on federationEnabled at
startup. backgroundPrune drops rw *forwards from its effect set.
0 commit comments