You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since JRuby uses joda-time, which represents times using a signed long of milliseconds, it is impossible to represents Times larger than roughly (2**63-1)/1000 seconds.
It is not clear to me whether adding support for this in JRuby would be worthwhile, I would argue that raising a specific exception for timestamps beyond the limit would be a lot better than the above seemingly random behaviour.
The text was updated successfully, but these errors were encountered:
It is a compatibility difference but one I do not see anyone hitting in real life and our hands are tied by joda time not working for unlimited precision. So I think WONTFIX :|
The behaviour of
Time.at
is inconsistent in MRI and JRuby.Since JRuby uses joda-time, which represents times using a signed long of milliseconds, it is impossible to represents
Time
s larger than roughly(2**63-1)/1000
seconds.It is not clear to me whether adding support for this in JRuby would be worthwhile, I would argue that raising a specific exception for timestamps beyond the limit would be a lot better than the above seemingly random behaviour.
The text was updated successfully, but these errors were encountered: