Kyle Meyer <k...@kyleam.com> writes: > I've sat down to work on it a few times and wasn't able to get anywhere > with the time I had available. It's on my list to revisit. However, as > we have no proposed fix, in my view it'd make sense to revert the > problematic commit, 39c656870. While that recent commit may resolve a > longstanding bug in the handling of one-time delays, it causes a > regression in functionality that I suspect is much more widely used and > relied on. > > I'll plan to revert the commit tomorrow. Please chime in if you > disagree with me doing so.
Reverted in 1de7eabf2.
