Patterns with future years should not limit the day and month range (#…

…116)

* Patterns with future years should not limit the day and month range
* Test does not depend on Utc::now()

src/schedule.rs

@@ -36,6 +36,11 @@ impl Schedule {
             .range((Included(query.year_lower_bound()), Unbounded))
             .cloned()
         {
+            // It's a future year, the current year's range is irrelevant.
+            if year > after.year() as u32 {
+                query.reset_month();
+                query.reset_day_of_month();
+            }
             let month_start = query.month_lower_bound();
             if !self.fields.months.ordinals().contains(&month_start) {
                 query.reset_month();
@@ -548,6 +553,22 @@ mod test {
         assert_eq!(prev2, next2);
     }
 
+    #[test]
+    fn test_next_after_past_date_next_year() {
+        // Schedule after 2021-10-27
+        let starting_point = Utc
+            .with_ymd_and_hms(2021, 10, 27, 0, 0, 0)
+            .unwrap();
+
+        // Triggers on 2022-06-01. Note that the month and day are smaller than
+        // the month and day in `starting_point`.
+        let expression = format!("0 5 17 1 6 ? 2022");
+        let schedule = Schedule::from_str(&expression).unwrap();
+        let next = schedule.next_after(&starting_point);
+        println!("NEXT AFTER for {} {:?}", expression, next);
+        assert!(next.is_some());
+    }
+
     #[test]
     fn test_prev_from() {
         let expression = "0 5,13,40-42 17 1 Jan *";