| Summary | Infinite loop for events spanning month end/beginning |
| Queue | Kronolith |
| Queue Version | HEAD |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | Horde Developers (at) |
| Requester | kevin_myer (at) iu13 (dot) org |
| Created | 07/27/2005 (7290 days ago) |
| Due | |
| Updated | 08/01/2005 (7285 days ago) |
| Assigned | 07/27/2005 (7290 days ago) |
| Resolved | 08/01/2005 (7285 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Resolved
New Attachment: kronolith.diff
I've got the same problem and found out that the problem is a ++mday
in Kronolith::_getEvents for non-repeating events where there is no
$loopDate->correct() call and therefor the day of month is increased
infinitely.
Please find attached a correcting diff for HEAD branch as well as
FRAMEWORK_3 branch (cvs).
State ⇒ Assigned
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Infinite loop for events spanning month end/beginning
Queue ⇒ Kronolith
Following 1.295 commit of lib/Kronolith.php (
http://cvs.horde.org/diff.php/kronolith/lib/Kronolith.php?r1=1.294&r2=1.295&ty=u) the following event sends Kronolith into an infinite
loop:
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//The Horde Project//Horde_iCalendar Library //EN
METHOD:PUBLISH
BEGIN:VEVENT
DTSTART;VALUE=DATE:20050630
DTEND;VALUE=DATE:20050701
DTSTAMP:20050726T162753Z
UID:20050611203716.1ea4s0f39lfk@example.com
SUMMARY:Personal Day
TRANSP:OPAQUE
ORGANIZER;CN=First Last:MAILTO:first_last@example.com
CATEGORIES:Personal
END:VEVENT
END:VCALENDAR