• (nodebb)

Somebody added 0.01 to 0.06 and got a number ever so slightly smaller than 0.07, computers(1) being what they are.

(1) By which I mean bad programmers, of course.

• (nodebb)

If we're going to be pedantic, there are two problems with the error message in the frist one.

The easy one is that a time interval is always between 1 and 24 hours or always not between 1 and 24 hours no matter what time unit you convert it to.

The other one is that frequency and interval have different dimensions. Frequency is not measured in hours or milliseconds, but 1/hours or 1/milliseconds.

• Industrial Automation Engineer (unregistered)

is it that the error message seems to suggest that a conversion to milliseconds may alter the duration?

• DaveD (unregistered)

"24 is not between 1 and 24!" It is in SQL

• tank0r (unregistered)

I am BEGGING beer and applesauce guy to press "go to recipe". I need to see it.

• Benjamin (unregistered)

Well, the legal agreement doesn't say anything about first born children so, I'd accept it, why not

• A Scourge (unregistered)

The fridge is part of a scourge of crappy ML spreading across the world. If you thought people were efficient at bloating the internet with garbage, just wait until you see what content-generating neural net's can do!

• Heinebold (unregistered) in reply to Industrial Automation Engineer

For inputting fixed intervals, that seems unlikely, especially when nothing over 24h is allowed. But if you may enter months or other variable "units", thing like that could happen.

• markm (unregistered)

The first item is 3 WTFs in one!

1. Bad programming allows input validation to fail from floating point rounding errors in multiplying 24 hours out to get milliseconds (24.0 * 60 * 60 * 1000). It doesn't matter whether the validation comparison should have been "less than" or "less than or equal" when using floating point, because after calculations quantities that should be equal usually aren't, and sometimes quantities that should be slightly different are equal. A programmer that doesn't compensate for that should not be allowed to use floating point.

The second item in the original post (Huntington sales tax) also looks like floating point error.

1. "Period", not "frequency".

2. Did they really want 1 to 24 hours, or 0 to 24 hours, or something like 0.00001 to 24.0000 hours?