fix: Duration.decode and Duration.times throwing on fractional values#6270
Open
chatman-media wants to merge 1 commit into
Open
fix: Duration.decode and Duration.times throwing on fractional values#6270chatman-media wants to merge 1 commit into
chatman-media wants to merge 1 commit into
Conversation
🦋 Changeset detectedLatest commit: f2fd0b9 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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.
What
Two related crashes in
Durationwhen given fractional values, both caused by passing a non-integer toBigInt():1.
Duration.decode("1.5 nanos" | "1.5 micros")throwsDURATION_REGEXexplicitly permits a decimal mantissa (-?\d+(?:\.\d+)?), so the input passes validation. But thenanos/microsbranches pass the raw matched string straight toBigInt:Every other unit (
millis,seconds, …) usesNumber(valueStr)and works fine with decimals (there's already a passing test for"1.5 seconds"). Onlynanos/microscrash.2.
Duration.times(nanosDuration, 2.5)throwstimesis typed to accept anynumbermultiplier, but the nanos branch does:So multiplying a nanosecond-backed
Durationby a non-integer throws, despite the type signature allowing it.Fix
decode: fornanos/micros, when the value is fractional, scale to whole nanoseconds and round (nanos is the smallest representable unit). Integer inputs keep the existingBigInt(valueStr)path, preserving exact values for large integers (e.g."99999999999999999999 nanos")."1.5 micros"->1500nanos"1.5 nanos"->2nanos"-1.5 nanos"->Duration.zero(consistent with existing"-1.5 seconds"->zero)times: keep exact bigint multiplication for integer multipliers (no precision loss for large durations); fall back to roundedNumbermath only for non-integer multipliers.Duration.times(Duration.nanos(2n), 2.5)->5nanosTests
Added cases to the existing
decodeandtimestests. Both fail onmain(SyntaxError: Cannot convert 1.5 to a BigInt/RangeError: ... not an integer) and pass with the fix. FullDurationsuite (48 tests), SchemaDurationsuite, andSchedulesuite all pass;tsc -bandeslintare clean.Part of #4349.