https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39748 --- Comment #32 from David Cook <dcook@prosentient.com.au> --- (In reply to Lisette Scheer from comment #9)
(In reply to Katrin Fischer from comment #8)
Yes, that's correct.
We're running into a similar problem with a cron we run between 2-3 am, and the us changes happens at 2 am so we lose that hour.
DateTime recommends doing calculations in UTC according to https://metacpan.org/pod/DateTime#How-DateTime-Math-Works (found from this issue on the GitHub https://github.com/houseabsolute/DateTime.pm/issues/21)
You'll want to scrolldown a bit more on CPAN there to "math on non-UTC time zones". Sometimes, the right answer is to convert to UTC, and sometimes the right answer is to use a floating timezone. If you're doing datetime math where you're using the result of the math as a datetime itself, you probably want to use UTC. However, in this case, we're just checking to see if the "dateexpiry" is before midnight of the current date. In that case, things get more complicated. If we convert to UTC, it's possible that the current date could actually be the day before the real current date (this is common in Australia where we're many hours ahead of GMT - we cross UTC midnight around 10/11am depending on the time of year). -- You are receiving this mail because: You are watching all bug changes.