tracker issue : CF-3641349

select a category, or use search below
(searches all categories and all time range)

timeformat and daylight savings with numeric dates

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Aaron Shurmer / Aaron Shurmer (Aaron Shurmer)

Created: 09/29/2013

Components: Language

Versions: 10.0

Failure Type:

Found In Build/Fixed In Build: Final /

Priority/Frequency: Major / Some users will encounter

Locale/System: English / Win 2008 Server R2 64 bit

Vote Count: 1

Listed in the version 2016.0.0.297996 Issues Fixed doc
Verification notes: verified_fixed on August 26, 2019 using build 2016.0.01.298513
Problem Description: 
time format stuffs up with numeric date on daylight savings days. machine locale set to new zealand en_NZ java locale
#timeformat( 41546.9166667, "HH:MM" )# returns 11:00pm, should return 10:00pm

timeformat( 41545.9166667, "HH:MM" ) returns 10:00pm
timeformat( 41546.9166667, "HH:MM" ) returns 11:00pm <- which is quite wrong
timeformat( 41547.9166667, "HH:MM" ) returns 10:00pm

Steps to Reproduce:
set locale to new zealand, run 3 statements above

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3641349

External Customer Info:
External Company:  
External Customer Name: AaronShurmer
External Customer Email:  
External Test Config: My Hardware and Environment details:



+1. I don't see how the time part of the number should be impacted by DLS one way or the other! 0.91666 is 22hrs, not 23hrs. I could see how an adjustment might be made during the cross-over period when an hour doesn't actually exist when clocks go forward, but that's not 10-11pm. -- Adam
Vote by External U.
14426 | September 29, 2013 03:56:14 AM GMT
works fine. Are you still facing the issue?
Comment by Suchika S.
14421 | December 18, 2013 08:04:25 AM GMT
Yip, still happening.
Comment by External U.
14422 | January 23, 2014 04:19:19 PM GMT
Hi, Can you let us know you are on which update ? Also have you tried on the latest builds of CF10 n CF11? I tried on latest updates of 10 and 11 and I cannot repro the bug. Thanks, Suchika.
Comment by Suchika S.
14423 | December 10, 2014 05:21:48 AM GMT
did you try it with your server date set to a daylight savings changeover day?
Comment by External U.
14424 | December 10, 2014 04:06:42 PM GMT
Checked on the daylight savings day for 11. It is not an issue there. But the issue exist on CF10 . We will evaluate the fix and let you know if it can be available on the latest update of CF10.
Comment by Suchika S.
14425 | December 11, 2014 01:07:13 AM GMT
Hi Adobe, I've verified this is fixed in CF2016 Update 1 (build 2016.0.01.298513). If current TZ honors DST (ex: -Duser.timezone=NZ or -Duser.timezone=America/New_York in jvm.config), then CF10 (build and CF11 (build incorrectly convert datetime numbers (by adding the DST offset amount) to datetime objects if they 1) occur on a DST changeover day -and- 2) occur after the DST changeover. Thanks!, -Aaron
Comment by Aaron N.
31214 | August 26, 2019 04:11:32 AM GMT