getOccurrencesAfter doesn't work with microseconds

[edalzell]

Hey there, not sure if this an actual bug.

I have found that if I set the dtstart to a time with microseconds (like 23:59:59.999999), then the nextOccurrencesAfter will return the next day's occurrence and not today's occurrence.

Once I remove the microseconds, it works fine.

I'm setting dtstart to a Carbon instance:

Where endTime() was now()->endOfDay()->toTimeString('microsecond').

[rlanvin]

Hello, it's a bit hard to tell what's happening with the code your provided and without the exact rule, and on top of that nextOccurrencesAfter isn't part of this library, so I'm really confused.

Please provide the following:

• Reproducible code demonstrating the bug (including the rule), so I can try myself
• An example of expected behaviour vs actual behaviour
• The exact version of the library your are using

Thank you!

[edalzell]

With microseconds:

Without microseconds:

Notice in the first screenshot, it shows TOMORROW (today is the 14th) and the second is correct.

Version rlanvin/php-rrule v2.3.0

[rlanvin]

Thank you for the details. Microseconds are known to cause issues with date comparison. The microsecond component was intended to be removed from the input, but you found a bug. I published version 2.3.1 which fixes this issue.

[edalzell]

Awesome, thanks for the quick fix. Love this package!