[asterisk-bugs] [Asterisk 0017877]: [patch] Merging events for Exchange web service doesn't work as expected, resulting in only one event in calendar

Asterisk Bug Tracker noreply at bugs.digium.com
Mon Aug 23 17:50:50 CDT 2010


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17877 
====================================================================== 
Reported By:                pitel
Assigned To:                twilson
====================================================================== 
Project:                    Asterisk
Issue ID:                   17877
Category:                   Resources/res_calendar
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     ready for review
Target Version:             1.8.0
Asterisk Version:           SVN 
JIRA:                       SWP-2063 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 282538 
Request Review:              
====================================================================== 
Date Submitted:             2010-08-17 07:14 CDT
Last Modified:              2010-08-23 17:50 CDT
====================================================================== 
Summary:                    [patch] Merging events for Exchange web service
doesn't work as expected, resulting in only one event in calendar
Description: 
I just noticed that when I have multiple events in EWS calendar, only one
is merged. And I found a strange behaviour of ast_calendar_merge_events().

I added a little debug output (in attached patch) and get this result:

--
AQAPAHRlc3RmaXRAaXBleC5jegBGAAADyTdZ3ABu8EOjYAFhV6KsHgcA+GG41xCdl025mKVi8islNgAAAx0AAABc2kyxph+ESpyNgxlJiF/xAAABHppPAAAA:
AAA
++
AAAPAHRlc3RmaXRAaXBleC5jegFRAAgIzQu2RRQAAEYAAAAAyTdZ3ABu8EOjYAFhV6KsHgcA+GG41xCdl025mKVi8islNgAAAAAAHQAAdAXzuHYsTEahylQnDZcWqAAPO7o49gAAEA==:
BBB
--
AAAPAHRlc3RmaXRAaXBleC5jegFRAAgIzQu2RRQAAEYAAAAAyTdZ3ABu8EOjYAFhV6KsHgcA+GG41xCdl025mKVi8islNgAAAAAAHQAAdAXzuHYsTEahylQnDZcWqAAPO7o49gAAEA==:
BBB
++
AQAPAHRlc3RmaXRAaXBleC5jegBGAAADyTdZ3ABu8EOjYAFhV6KsHgcA+GG41xCdl025mKVi8islNgAAAx0AAABc2kyxph+ESpyNgxlJiF/xAAABHppPAAAA:
AAA

-- in beggining of line means the event is removed from our internal
calendat, ++ means it was added and there should be also == which means it
was merged. Every action follows by UID of event, colon and name of event.

As you can, the event AAA is removed, event BBB is added, then removed and
then is event AAA added again, resulting in only event AAA being in
internal calendar.

I really don't know why is this happening, since UID is compared with
known events, and then is decided if we know if this event already exist or
not. And appereantly, the UIDs match, so I have really no idea why it
results in removing and adding the same event instead of merging.

And just for infomration, icalendar modul works as expected, merging
already known events.
====================================================================== 

---------------------------------------------------------------------- 
 (0126244) lmadsen (administrator) - 2010-08-23 17:50
 https://issues.asterisk.org/view.php?id=17877#c126244 
---------------------------------------------------------------------- 
pitel: awesome -- it'd probably be easiest for you to jump on IRC and join
#asterisk-dev and speak with jpeeler about getting a certificate so you can
do commits, and to speak with the developers about your first round of
commits. This way people can help you move through the review process and
make sure you get a Ship It! and then perform your commits to 1.8 and
trunk.

Thanks! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-08-23 17:50 lmadsen        Note Added: 0126244                          
======================================================================




More information about the asterisk-bugs mailing list