Tickets :: [#10951] Catch Horde_Exception_NotFound on Kronolith Api

unknown

5/18/25

Summary	Catch Horde_Exception_NotFound on Kronolith Api
Queue	Kronolith
Queue Version	Git master
Type	Bug
State	Resolved
Priority	1. Low
Owners	jan (at) horde (dot) org
Requester	goncalo.queiros (at) portugalmail (dot) net
Created	02/01/2012 (4855 days ago)
Due
Updated	02/01/2012 (4855 days ago)
Assigned
Resolved	02/01/2012 (4855 days ago)
Milestone
Patch	Yes

02/01/2012 07:56:06 PM	Git Commit	Comment #3	Reply to this comment
Changes have been made in Git (refs/heads/develop): commit af3818d917b5a143363b60ff31eebdc1560ea7f8 Author: Gonçalo Queirós <goncalo.queiros@portugalmail.net> Date: Wed Feb 1 11:29:28 2012 +0000 Catch Horde_Exception_NotFound exceptions when looking for events on Kronolith Api Signed-off-by: Jan Schneider <jan@horde.org> ~~Bug: 10951~~ kronolith/lib/Api.php \| 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) http://git.horde.org/horde-git/-/commit/af3818d917b5a143363b60ff31eebdc1560ea7f8

02/01/2012 02:28:30 PM	Jan Schneider	Assigned to Jan Schneider State ⇒ Resolved

02/01/2012 02:24:54 PM	Git Commit	Comment #2	Reply to this comment
Changes have been made in Git (refs/heads/master): commit af3818d917b5a143363b60ff31eebdc1560ea7f8 Author: Gonçalo Queirós <goncalo.queiros@portugalmail.net> Date: Wed Feb 1 11:29:28 2012 +0000 Catch Horde_Exception_NotFound exceptions when looking for events on Kronolith Api Signed-off-by: Jan Schneider <jan@horde.org> ~~Bug: 10951~~ kronolith/lib/Api.php \| 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) http://git.horde.org/horde-git/-/commit/af3818d917b5a143363b60ff31eebdc1560ea7f8

02/01/2012 12:25:00 PM	goncalo (dot) queiros (at) portugalmail (dot) net	Comment #1 Priority ⇒ 1. Low New Attachment: 0001-Catch-Horde_Exception_NotFound-exceptions-when-looki.patch Patch ⇒ Yes Milestone ⇒ Queue ⇒ Kronolith Summary ⇒ Catch Horde_Exception_NotFound on Kronolith Api Type ⇒ Bug State ⇒ Unconfirmed	Reply to this comment
This problem can be seen, if you add an event on the client, sync, and then (without any other syncronization) delete it from Kronolith. On the next sync, the Exception will not be detected by the getChanges function on the Kronolith API, and the delete will never be sent to the client.