Tickets :: Comment on [#14453] Allowed memory size exhausted

* Your Email Address
* Spam protection	Enter the letters below: . ..___..___. ..___. \|_/ _/ [__ \|\/\| _/ \| \./__.\| \| \|./__.
Comment	> Changes have been made in Git (master): > > commit 4bd7428e438a50537882c70e1a71f90a963ff856 > Author: Michael J Rubinsky <mrubinsk@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
Attachment
Watch this ticket