| Summary | Infinite loop because of a recurring event |
| Queue | Kronolith |
| Queue Version | FRAMEWORK_3 |
| Type | Bug |
| State | Resolved |
| Priority | 3. High |
| Owners | wrobel (at) horde (dot) org |
| Requester | chuck (at) horde (dot) org |
| Created | 11/12/2009 (5712 days ago) |
| Due | |
| Updated | 11/27/2009 (5697 days ago) |
| Assigned | |
| Resolved | 11/27/2009 (5697 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Resolved
Sorry for the long delay in fixing this. Should be resolved now.
In FW3 dates need to be corrected after modifying them. Missed one
such call.
Bug #8702: Infinite loop because of a recurring event.http://cvs.horde.org/diff.php/kronolith/lib/Attic/Recurrence.php?rt=horde&r1=1.16.2.11&r2=1.16.2.12&ty=u
In FW3 dates need to be corrected after modifying them. Missed one
such call.
Bug #8702: Infinite loop because of a recurring event.http://cvs.horde.org/diff.php/framework/Date/Date/Attic/Recurrence.php?rt=horde&r1=1.7.2.13&r2=1.7.2.14&ty=u
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ Infinite loop because of a recurring event
Queue ⇒ Kronolith
Assigned to Gunnar Wrobel
Milestone ⇒
Patch ⇒ No
State ⇒ Assigned
importing the attached file. The file is anonymized calendar data from
my family, limited to recurring events. This does *not* happen in git
code, and it was introduced after Nov. 9th - I can see the affected
calendars fine in either current git, or by running:
cvs up -r FRAMEWORK_3 -D 2009-11-09 kronolith
In my FW_3 checkout.