Time Zone Bug ('Antarctica/DumontDUrville')

[Lonniebiz]

There is a timezone bug in Node 10.16.0. It is the same bug that I reported to Chromium here:
https://bugs.chromium.org/p/chromium/issues/detail?id=928068

Run the code in comment 1, from there, to reproduce the bug in Node 10.16.0.

I'm not sure if this is a V8 thing or if each environment has to fix the bug. If it is a V8 thing, perhaps this bug will go away by itself eventually. Otherwise, it needs to be addressed in Node.

[cjihrig]

This is a V8 thing that got fixed in Node 12.5.0 via the V8 update.

[bnoordhuis]

Antarctica/DumontDurville was fixed in commit v8/v8@2cf79d12e8 and could be back-ported to the v10.x branch.

Asia/Qostanay requires an ICU update because that's where we get the tzdata from.

[srl295]

@Lonniebiz as to Asia/Qostanay — you can check the tz version with node -p process.versions.tz, Asia/Qostanay was added in 2018i which is there by default in ICU ≥64.1 ICU-20331

I just checked Node 10.16.3 and it has ICU 64.2 and tz 2019a. I think we should close this as already fixed in v10.16.0 by b323658 / #27361

[srl295]

Whoops. the original issue is still there in v10.x. Reopening.

new Date().toLocaleString("en-US", {timeZone: "Antarctica/DumontDUrville"});

[Lonniebiz]

This bug just adds proof that the earth is flat. This is a fictitious timezone anyway, so don't bother fixing this.

[jasnell]

does this need to remain open?

[jasnell]

Given that this is limited to 10.x and there will not be another 10.x release before it hits end of life in a few days, going ahead and closing this.

[srl295]

Sorry I didn't get back to this, but closing is the right path