Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[15] Bug Fix for infinite loop while trying to get next or prev occurrence #16

Conversation

siddarth-patil
Copy link
Owner

This is a fix for #15

  • Updated day_of_month_regex to only allow L-1 to L-30 and exclude L-31.
  • Updated __find_once and __find_prev_once to break infinite loop by returning None.
  • Added __is_valid_date validation inside __find_prev_once method to make sure valid date is returned.
  • Added required test cases.
  • Patch version Bump

…rence

- Updated `day_of_month_regex` to only allow `L-1` to `L-30` and exclude `L-31`.
- Updated `__find_once` and `__find_prev_once` to break infinite loop by returning `None`.
- Added `__is_valid_date` validation inside `__find_prev_once` method to make sure valid date is returned.
- Added required test cases.
- Patch version Bump
- Getting rid of `UTC` and `datetime` import as they are not supported in Python 38,39, and 310
@siddarth-patil siddarth-patil merged commit bde52fb into main Feb 18, 2025
10 checks passed
@siddarth-patil siddarth-patil deleted the 15-bug-infinite-loop-in-aws-cron-expression-parsing-with-invalid-l--syntax branch February 18, 2025 14:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG] Infinite Loop in AWS Cron Expression Parsing with Invalid L- Syntax
1 participant