Keep calendar rotation boundaries across clock changes - #171
Open
OskarEichler wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Calendar rotation currently advances midnight by fixed 86,400-second intervals, which can land at 23:00 or 01:00 across offset changes. Advance from local noon and reconstruct local midnight so daily and weekly boundaries remain calendar boundaries. The timezone model covers UTC, London, New York, Lord Howe and Apia from 2008–2028: baseline has 13 failures and the candidate has zero. Current suites pass 64 tests / 323 assertions on Ruby 4.0.6 and 3.2.11. No repository tests were changed.