-
Notifications
You must be signed in to change notification settings - Fork 30k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
deps: update timezone to 2023c #47680
Conversation
Kind of surpised by this one... ICU 73.1 already contains timezone 2023c. |
The PR/commit message is misleading, but it does appear to remove an unneeded file, I think? |
I doesn't remove the file. It reduces its size (probably by removing some data in it). |
/cc @srl295 |
It should perhaps check process.versions.tz before running. |
Maybe just a re pack. I'll check it sometime today. |
in renameSync(`icu-data/tzdata/icunew/${latestVersion}/44/le/${file}`, `deps/icu-small/source/data/in/${file}`); this should be a copy instead of a move. Otherwise it's destructive to the |
uncompressed the files are identical in size (but different in content) so the 500 byte 'reduction' was a recompression.
./tools/icu/shrink-icu-src.py has # compression stuff. Keep the suffix and the compression function in sync.
compression_suffix = '.bz2'
def compress_data(infp, outfp):
with open(infp, 'rb') as inf:
with bz2.BZ2File(outfp, 'wb') as outf:
shutil.copyfileobj(inf, outf) whereas execSync('bzip2 -z deps/icu-small/source/data/in/icudt*.dat'); |
also see #47302 |
ok my analysis tools are in #47248 (comment) (document somewhere?) $ diff ICU0/timezoneTypes.txt ICU1/timezoneTypes.txt
10d9
< camtr { "cator" }
35d33
< America:Montreal { "America/Toronto" }
308a307
> America:Montreal { "camtr" } this shouldn't have made a change, but it did. Investigating. Update This is a bad change (regression). |
@yumaoka any ideas here? Node.js has ICU4C 73.1, and this script "updated" it using https://github.com/unicode-org/icu-data/tree/main/tzdata/icunew/2023c/44 (It's a bug, because 73.1 is already at 2023c) But it looks like the
Is |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reverts data, So this should not be approved but closed.
(But need to sort out the tool and data issues)
Probably a better way to say it is: If there was a 2023d (always likely), it will undoubtably contain the CLDR 43 changes. Anyway, I propose to close this PR and fix issues in #47702 |
This PR was generated by tools/timezone-update.yml.
Updates the ICU files as per the instructions present in https://github.com/nodejs/node/blob/main/doc/contributing/maintaining-icu.md#time-zone-data
To test, build node off this branch & log the version of tz using