[Tickets #14453] Re: Allowed memory size exhausted

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: https://bugs.horde.org/ticket/14453
------------------------------------------------------------------------------
  Ticket             | 14453
  Updated By         | Git Commit <commits at lists.horde.org>
  Summary            | Allowed memory size exhausted
  Queue              | Kronolith
  Version            | 4.2.17
  Type               | Bug
  State              | Assigned
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Git Commit <commits at lists.horde.org> (2016-08-26 16:49) wrote:

Changes have been made in Git (master):

commit 4bd7428e438a50537882c70e1a71f90a963ff856
Author: Michael J Rubinsky <mrubinsk at horde.org>
Date:   Fri Aug 26 12:44:23 2016 -0400

     Revert "Bug: 14453 Limit addCoverDates to the $endDate."

     This reverts commit 7695fc444ff10bd9950f0332c27c5c5874397d0a.

     This isn't correct. Setting $endDate to $event->end defeats the purpsose
     of this change when polling for alarms but removing that line
     will no longer return multi-day events that start before $startDate
     when no $endDate is provided.

     Not sure what the solution is here since when polling alarms we
     don't want an end date - no way of knowing the longest alarm interval
     that we have.

     Perhaps always limiting to some unrealistic time frame like 10 years
     would be sufficient for protecting against memory limits while still
     allowing reasonable alarm intervals to be supported?

  kronolith/lib/Kronolith.php | 14 ++++++--------
  1 file changed, 6 insertions(+), 8 deletions(-)

http://github.com/horde/horde/commit/4bd7428e438a50537882c70e1a71f90a963ff856