Correct fractional-hour offset conversion and display - #52
Open
OskarEichler wants to merge 5 commits into
Open
Conversation
Member
|
Okay, so basically you decided to ruin my weekend.
|
Member
|
What is this test wrecking crap? |
Member
|
Use |
Author
|
Updated the regression to use the project assert style and restored the final blank line. The focused module suite passes with 156 tests and 232 assertions. |
Member
|
Enumerate the rules in the project assert style in a comment in this pull request. |
OskarEichler
force-pushed
the
codex/fix-fractional-hour-offsets
branch
from
August 30, 2026 16:26
51a48eb to
c72d3de
Compare
Author
|
The project assertion rules I will follow are:
The current regression uses the two-argument equality form throughout, and |
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
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.
Summary
Correct three offset arithmetic/sign errors affecting non-whole-hour timezones:
Reproduction
EtOrbi.get_tzone(19800)currently returns nil because the internal formatter produces "+05:1800"; it now resolves +05:30 with an offset of 19800 seconds. Both 5:30 and 5:45, positive/negative half-hour values, and zero were checked.EtOrbi.get_tzone("-00:30")currently has a positive 1800-second offset; it now has -1800. Compact "-0030" was checked too.EtOrbi::EoTime.new(0, "Asia/Kolkata").to_debug_snow contains "+05:30", not "+05:1800".Verification
The current master's unreleased day-delta change was not brought into the consumer branch. No live scheduler or production operations were used. Linux/Windows and other Ruby runtimes were not run locally.
Breaking changes and limitations
No intended API break; malformed/reversed results become the correct offset. Existing whole-hour behavior is preserved. This does not expand the accepted hour range or add second-resolution numeric timezone support. Checked current source, open PRs and offset-related issues before publication.