max / makenotwork

pom: set MissedTickBehavior::Delay on the remaining probe loops health/tls/backup/scan_pipeline/prune/meta_alert/peer kept the default Burst, so after a stall or clock-jump they fired a catch-up storm of back-to-back checks (redundant load + recovery-spam). Delay matches the four loops that already set it (fuzz-2026-07-06 tick-storm). (scan_pipeline/meta_alert/health/peer are set in the following commits that also touch those files.)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: Max Johnson <me@maxj.phd> · 2026-07-07 17:09 UTC

Signed with PGP, not checked

Commit: 14b8adacbb4fe1dac296624b8aa64e771b63f23f

Parent: bfb4962

3 files changed, +3 insertions, -0 deletions

M pom/src/cli/tasks/backup.rs +1

			@@ -33,6 +33,7 @@
33	33		let mut interval = tokio::time::interval(
34	34		std::time::Duration::from_secs(interval_secs),
35	35		);
	36	+	interval.set_missed_tick_behavior(tokio::time::MissedTickBehavior::Delay);
36	37		interval.tick().await; // consume immediate first tick
37	38		loop {
38	39		tokio::select! {

M pom/src/cli/tasks/prune.rs +1

			@@ -15,6 +15,7 @@
15	15		let mut interval = tokio::time::interval(
16	16		std::time::Duration::from_secs(86400),
17	17		);
	18	+	interval.set_missed_tick_behavior(tokio::time::MissedTickBehavior::Delay);
18	19		interval.tick().await; // consume immediate first tick
19	20		loop {
20	21		tokio::select! {

M pom/src/cli/tasks/tls.rs +1

			@@ -31,6 +31,7 @@
31	31		let mut interval = tokio::time::interval(
32	32		std::time::Duration::from_secs(tls_interval_secs),
33	33		);
	34	+	interval.set_missed_tick_behavior(tokio::time::MissedTickBehavior::Delay);
34	35		interval.tick().await; // consume immediate first tick
35	36		loop {
36	37		tokio::select! {