Bad DST after 2038

[dickermoshe]

final ianaTz = Timezone.timezoneProvider['America/New_York']!;
var dt = DateTime.parse('2038-03-14 03:00:00.000');
while (dt.year < 2050) {
  final ianaSpan = ianaTz.span(at: dt.microsecondsSinceEpoch);
  print(ianaSpan.offset);
  dt = dt.add(const Duration(minutes: 30));
}

The above will always print -5.
Before 2038 it all works great

[Pante]

Seems like the timezone data is truncated after 2037. This can be either because IANA doesn't provide timezone data pass that yet or something related to the Year 2038 problem. I'm concerned since we internally use the timezone package to decode the zicfiles and might be an issue upstream.

EDIT:
Seems like thetimezone package has the same limitation. Checking https://tzexplorer.org/#/history reveals that there's timezone data until 2044 (unless the website is hallucinating but is very unlikely). So it's probably an upstream issue in timezone's zicfile parsing.

[dickermoshe]

I contains data until 1800-2092, they only show until 2044

[dickermoshe]

https://github.com/kshetline/tubular_time_tzdb#readme seems like a mature aina compiler which should be used instead of timezone.

I made major progress yesterday on the windows ffi implementation, working on unix today