https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39748 --- Comment #28 from David Cook <dcook@prosentient.com.au> --- (In reply to jonadab.theunsightlyone@gmail.com from comment #27)
Report filed upstream for the DateTime people: https://github.com/houseabsolute/DateTime.pm/issues/155
No idea when they will act on this (and even if they do, it may only be to document truncate() as unsafe in certain cases), so carry on as before.
As I note on the Github issue, I don't think this is actually a DateTime bug. It's just the reality of working with (local) time. (In reply to David Cook from comment #22)
In Koha/Patron.pm we should probably return 0 if $self->dateexpiry =~ '^0000' as well...
And then yeah... We should be able to safely assume that $self->dateexpiry is an ISO timestamp in the local timezone, then convert to either UTC or floating, clone it, and then do the date truncation
My earlier suggestion is a reasonable thing to do. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.