See other PR, we use a default of 0 for the alert notification debounce setting to indicate no debounce

@misberner which other PR?

See other PR, we use a default of 0 for the alert notification debounce setting to indicate no debounce

I do see we use 0 for ROX_ALERT_RENOTIF_DEBOUNCE_DURATION and ROX_RECORDER_DURATION (which I don't think is used anymore?). That being said, allowing 0 makes sense, but I do feel there are times where 0 should not be allowed. I wonder if I should add an option to allow/disallow 0. What do you think?

PR to remove ROX_RECORDER_DURATION #3559

Images are ready for the commit at b1a99f1.

To use with deploy scripts, first export MAIN_IMAGE_TAG=3.72.x-423-gb1a99f16a0.

@misberner which other PR?

I got two separate email threads because you renamed the PR, so I just assumed it was a different PR :) was on my phone

I wonder if I should add an option to allow/disallow 0. What do you think?

Hmm, personally I would think that disallowing 0 durations should happen at the level of the logic that consumes the duration setting. But I guess you could make the case that a 0 duration that is not intercepted can be very dangerous when it leads to code running in a loop with no delay when there should be a delay between iterations, and thus consuming insane amounts of CPU. Therefore, yeah, I think it makes sense to prescribe that a 0 duration has to be allowed explicitly.