[Tickets #12160] Re: Infinity loop on event with recurrence

[noreply at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/12160
------------------------------------------------------------------------------
  Ticket             | 12160
  Updated By         | Thomas Jarosch <thomas.jarosch at intra2net.com>
  Summary            | Infinity loop on event with recurrence
  Queue              | Kronolith
  Version            | Git master
  Type               | Bug
  State              | Unconfirmed
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Thomas Jarosch <thomas.jarosch at intra2net.com> (2013-04-15 10:05) wrote:

> Hm. Though ActiveSync also sets cover_dates to false, so that code  
> should never even be hit.  Can you use Horde::debug($message);  
> instead of your custom file output? This will give a backtrace as  
> well so we can see what the code path was.

Here you go:

Backtrace:
  1. Horde_Rpc_ActiveSync->getResponse()  
/datastore/DEVEL/horde/horde/rpc.php:156
  2. Horde_ActiveSync->handleRequest()  
/datastore/DEVEL/horde/framework/Rpc/lib/Horde/Rpc/ActiveSync.php:141
  3. Horde_ActiveSync_Request_Base->handle()  
/datastore/DEVEL/horde/framework/ActiveSync/lib/Horde/ActiveSync.php:642
  4. Horde_ActiveSync_Request_Sync->_handle()  
/datastore/DEVEL/horde/framework/ActiveSync/lib/Horde/ActiveSync/Request/Base.php:218
  5. Horde_ActiveSync_Sync->syncronize()  
/datastore/DEVEL/horde/framework/ActiveSync/lib/Horde/ActiveSync/Request/Sync.php:794
  6. Horde_Core_ActiveSync_Driver->getMessage()  
/datastore/DEVEL/horde/framework/ActiveSync/lib/Horde/ActiveSync/Sync.php:213
  7. Horde_Core_ActiveSync_Connector->calendar_export()  
/datastore/DEVEL/horde/framework/Core/lib/Horde/Core/ActiveSync/Driver.php:676
  8. Horde_Registry_Caller->export()  
/datastore/DEVEL/horde/framework/Core/lib/Horde/Core/ActiveSync/Connector.php:96
  9. Horde_Registry_Caller->__call()  
/datastore/DEVEL/horde/framework/Core/lib/Horde/Core/ActiveSync/Connector.php:96
10. Horde_Registry->call()  
/datastore/DEVEL/horde/framework/Core/lib/Horde/Registry/Caller.php:41
11. Horde_Registry->callByPackage()  
/datastore/DEVEL/horde/framework/Core/lib/Horde/Registry.php:1043
12. call_user_func_array()  
/datastore/DEVEL/horde/framework/Core/lib/Horde/Registry.php:1086
13. Kronolith_Api->export()
14. Kronolith_Event->toASAppointment()  
/datastore/DEVEL/horde/kronolith/lib/Api.php:802
15. Kronolith_Driver->search()  
/datastore/DEVEL/horde/kronolith/lib/Event.php:1602
16. Kronolith_Driver->listEvents()  
/datastore/DEVEL/horde/kronolith/lib/Driver.php:164
17. Kronolith_Driver_Kolab->_listEvents()  
/datastore/DEVEL/horde/kronolith/lib/Driver.php:308
18. Kronolith::addEvents()  
/datastore/DEVEL/horde/kronolith/lib/Driver/Kolab.php:283
19. Horde::debug() /datastore/DEVEL/horde/kronolith/lib/Kronolith.php:456


-> kronolith/lib/Driver.php:search() does not pass any options to  
listEvents().
So $cover_date is true in this case.