Resolve ambiguity for permanent timezone changes #155
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Biz::Time
already passes true as thedst
parameter tolocal_to_utc
to avoid the ambiguity of converting a local time that occurred twice due to daylight savings time.However if a local time occurs twice due to a permanent timezone change, the
dst
parameter doesn't help.local_to_utc
can be given a block to handle this case:https://github.com/tzinfo/tzinfo/blob/v2.0.6/lib/tzinfo/timezone.rb#L613-L619
I encountered this problem due to a recent timezone change in Kazakhstan:
https://mm.icann.org/pipermail/tz-announce/2024-February/000081.html
I used an older example in the test so that it doesn't require the latest tz database.