Hi Iana, It appears that there is a typo in the latest version of tzdata (2024b), where one of the lines in northamerica should be "Apr" instead of "April". # Rule NAME FROM TO - IN ON AT SAVE LETTER/S Rule Mexico 1931 only - April 30 0:00 1:00 D Would you please check and see if it can be corrected in the next version? Thanks, Kelvin [Insignia-transp] Kelvin Wong VP, Client Services, FlexTrade Systems O: +852 3579 2231 | M: +852 3579 2231 | flextrade.com<http://flextrade.com/> 21/F, New World Tower 1, 16-18 Queen's Road Central, Hong Kong [cid:image002.png@01DB02CD.CF076080]<https://www.linkedin.com/company/flextrade/> [cid:image003.png@01DB02CD.CF076080] This communication is for informational purposes only. The contents of this transmission are confidential and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify the sender by return email and delete this message from your system. FlexTrade Systems Inc., its subsidiaries and affiliates do not guarantee the completeness and accuracy of this transmission's contents. Moreover, FlexTrade Systems Inc., its subsidiaries and affiliates do not guarantee this communication to be free of viruses and accept no liability for any damage caused thereof.
On Mon, 9 Sept 2024 at 15:45, Kelvin Wong via tz <tz@iana.org> wrote:
Hi Iana,
It appears that there is a typo in the latest version of tzdata (2024b), where one of the lines in *northamerica* should be “Apr” instead of “April”.
# Rule NAME FROM TO - IN ON AT SAVE LETTER/S
Rule Mexico 1931 only - April 30 0:00 1:00 D
Would you please check and see if it can be corrected in the next version?
It already has been, see the multiple emails about it in the past few days: https://lists.iana.org/hyperkitty/list/tz@iana.org/thread/6PF5BB7342JR6PALTM...
On 2024-09-09 08:34, Kelvin Wong via tz wrote:
Hi Iana,
It appears that there is a typo in the latest version of tzdata (2024b), where one of the lines in /northamerica/ should be “Apr” instead of “April”.
# Rule NAME FROM TO - IN ON AT SAVE LETTER/S
Rule Mexico 1931 only - April 30 0:00 1:00 D
Would you please check and see if it can be corrected in the next version?
Thanks, Kelvin
The maintainer is aware of it. The proposed change has already been added to the development git repository. I don't know if there will be a 2024c release to help silence all the bug reports. Technically, it isn't a bug in tzdata. It's just that the full month names break the current Java tzupdater utility. -- -=( Ian Abbott <abbotti@mev.co.uk> || MEV Ltd. is a company )=- -=( registered in England & Wales. Regd. number: 02862268. )=- -=( Regd. addr.: S11 & 12 Building 67, Europa Business Park, )=- -=( Bird Hall Lane, STOCKPORT, SK3 0XA, UK. || www.mev.co.uk )=-
One can point the tzupdater tool to a custom tzdata bundle URL containing the corrected line/patch using the '-l' option. https://www.oracle.com/java/technologies/javase/tzupdater-readme.html#usage One such custom 2024b bundle is available at https://bugs.openjdk.org/secure/attachment/110991/tzdata2024b-modified.tar.g... (one should probably inspect it before using it) i.e. following command would workaround the tzupdater issue java -jar tzupdater.jar -l https://bugs.openjdk.org/secure/attachment/110991/tzdata2024b-modified.tar.g... regards, Sean. On 09/09/2024 16:40, Ian Abbott via tz wrote:
The maintainer is aware of it. The proposed change has already been added to the development git repository. I don't know if there will be a 2024c release to help silence all the bug reports. Technically, it isn't a bug in tzdata. It's just that the full month names break the current Java tzupdater utility.
Hi @Ian Abbott, As mentioned in https://lists.iana.org/hyperkitty/list/tz@iana.org/thread/2HWC6NY5AFI63RRRJ2... It impacted our agent heavily and updating each agent is not a feasible solution for us. Could you provide the estimated ETA for 2024c release.
On 2024-09-09 11:40, sattisrinivas89--- via tz wrote:
Could you provide the estimated ETA for 2024c release.
There isn't any specific ETA for 2024c as this particular problem is not a serious one. As 2024b was released primarily for compatibility testing and doesn't have any urgent timestamp-related updates, if you can't use 2024b just stick with 2024a. There has been some work to fix what I think is your parser's issue. See: https://github.com/HowardHinnant/date/issues/836 which suggests some parser-specific workarounds. Although there is no ETA for fixing the parser, the workarounds should suffice.
Thanks for the reply @Paul Eggert, the problem is we have 1000's of agents in which the scheduler functionality is broken due to this due to this. The work arounds or making code fix and deploying them at scale will take considerable time. As fix is already been made, we would highly appreciate if a new version is released.
On Sep 9, 2024, at 1:24 PM, sattisrinivas89--- via tz <tz@iana.org> wrote:
Thanks for the reply @Paul Eggert, the problem is we have 1000's of agents in which the scheduler functionality is broken due to this due to this. The work arounds or making code fix and deploying them at scale will take considerable time. As fix is already been made, we would highly appreciate if a new version is released.
Can you deploy 2024a to those agents, as Paul suggested?
Hi Harris, Thanks for the reply. No we don't have that option. The library https://github.com/HowardHinnant/date will check for latest release and it auto downloads the latest version. With latest version and scheduler is broken. Most of the agents are private and we don't have access to them until the respective customer reach back to us. We are preparing a patch not to auto download but customers will take time to upgrade agents and until they do the system is down. We would really appreciate if a new patch - 2024c can be released, so that it would fix the problems immediately as fix has been made already.
participants (7)
-
Guy Harris -
Ian Abbott -
Jonathan Wakely -
Kelvin Wong -
Paul Eggert -
sattisrinivas89＠gmail.com -
Seán Coffey