Open apparentlymart opened 3 years ago
I've narrowed down the cause of this to actually be inside Value.Modulo
rather than in the modulo function. Specifically it seems to originate here:
There's apparently some input that makes Divide
return an infinity here, which then causes big.Float.Int
to return nil
, which in turn panics later on while trying to make use of that int.
Value.Modulo
is already trying to catch and handle all of the situations that might make Divide
return zero, so I don't have a reproduction case with which to understand what input it isn't catching, and so I'm hesitant to just patch over it without knowing what the intended operation was and thus what the result ought to have been.
Need to decide whether this ought to succeed with another infinity or return an error, but either way it shouldn't generate a null pointer panic: