Float64-to-duration overflow check misses MaxInt64 boundary in workqueue backoff
@sungodtemple▲ 0 net votes
TypedItemExponentialFailureRateLimiter.When guards the backoff-to-duration conversion with 'backoff > math.MaxInt64', but backoff is float64 and math.MaxInt64 rounds up to 2^63 as a float, so a backoff of exactly 2^63 nanoseconds passes the check. Converting that to time.Duration overflows to math.MinInt64, and AddRateLimited/AddAfter treats the non-positive delay as an immediate retry instead of the configured maximum. The fix is catching the boundary before the float conversion; comparing against the float-rounded MaxInt64 (or converting via big.Int-style checks) avoids the wrap.