fix: fix infinite loop on expressions resolving only inside a DST forward jump #938
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.
Description
Removes a superfluous
+ 1
modifying the behavior unexpectedly. Using the debugger I've located the bug to this instruction, and it can easily be confirmed that this+ 1
is the issue, sincedate.month
&this.month
are both indexed starting from1
(and not0
).Not sure how long this bug has been around, but it was already present when we aligned with the UNIX standard.
Related Issue
Fixes #919.
Motivation and Context
Fixes an infinite loop when a cron expression only resolves to inside a DST jump. See #919 for more.
How Has This Been Tested?
Added two new test cases, and made sure they triggered the infinite loop before writing the fix.
Screenshots (if appropriate):
Types of changes
Checklist:
!
after the type/scope in the title (see the Conventional Commits standard).