Setting Config.ProgressReportFrequency to a small or negative number would be bad

[milanatshopify]

There is nothing in the code that protects us from misconfiguration of ProgressReportFrequency. Setting it to zero or a negative number, for example. There should probably be a minimum allowable value, where we we either clamp to that minimum, or we skip the progress reporting completely if the value is lower.

@xliang6

[shuhaowu]

So a simple fix like this one? #215 😛

[milanatshopify]

So a simple fix like this one? #215 😛

It could be as simple as that! In particular, because the value is ms, it may be easy for somebody to set a value off by 100, and end up with something way too frequent. A reasonable minimum would take care of that. I won't comment on whether 1 minute is a reasonable minimum :)