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
It seems the bug was introduced in a2602aa#diff-5146f40a8c8111b14e5ab3407eff80c7a6d2f3c92a4bf4ccd4647bff32d47e38R1317-R1319 (although even back then, it did sometimes return an interval and sometimes a Duration.invalid()). In diff() and .diffNow() this has been subsequently fixed during a reimplementation, but until still exhibits the unexpected behaviour.
The text was updated successfully, but these errors were encountered:
When
.until(…)
is called on an invalidDatetime
instance, it returns the instance itself instead of an invalidInterval
.To Reproduce
It seems the bug was introduced in a2602aa#diff-5146f40a8c8111b14e5ab3407eff80c7a6d2f3c92a4bf4ccd4647bff32d47e38R1317-R1319 (although even back then, it did sometimes return an interval and sometimes a
Duration.invalid()
). Indiff()
and.diffNow()
this has been subsequently fixed during a reimplementation, butuntil
still exhibits the unexpected behaviour.The text was updated successfully, but these errors were encountered: