OBM
  1. OBM
  2. OBMFULL-5922

T#10053 T#10377 Some events aren't synchronized from OBM to Lightning

    Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Normal Normal
    • Resolution: Fixed
    • Affects Version/s: 2.5.7
    • Fix Version/s: 2.5.8
    • Component/s: opush, ui
    • Labels:
      None
    • Similar Issues:
      Show 10 results 
    • Rank:
      6136

      Description

      Information

      We don't know which event types/details trigger the issue, but two of our major clients do reproduce the issue. It's at least worth trying to reproduce.

      Tosca

      https://www.08000linux.com/lstm/issues/10377
      https://www.08000linux.com/lstm/issues/10053-Ev-nements-non-visibles-dans-TB

      1. obm-connector-log.txt
        30 kB
        Ba Tuan NGO
      2. obm-sync&opushLog.txt
        13 kB
        Ba Tuan NGO

        Issue Links

          Activity

          Hide
          Thomas HILAIRE added a comment -

          About the "opush set exception time at midnight" problem :
          When we developed that feature we just tried to clone the obm-ui behavior.
          What is wrong is that obm-ui has two different behaviors depending on the way used to create an exception.

          • at creation time: every exception start time is persisted as occurence.startTime in UTC
          • at modification time: every exception start time is persisted as occurence.midnightTime in UTC

          Exemple, in the database you can see exceptions of a daily recurrent event starting each 18h30 UTC+2:

          eventexception_parent_id eventexception_child_id eventexception_date
          109282   2014-09-14 16:30:00 exception created at event creation time by obm-ui (exception day 2014-09-14)
          109282   2014-09-10 22:00:00 exception created on already existing event by obm-ui (exception day 2014-09-11)

          Problem, obm-ui has two differents behaviors but it must have only one.
          Then opush and thunderbird must have the same behavior than obm-ui.
          I guess that the excepted behavior is to not set the exception date at midnight!

          Show
          Thomas HILAIRE added a comment - About the "opush set exception time at midnight" problem : When we developed that feature we just tried to clone the obm-ui behavior. What is wrong is that obm-ui has two different behaviors depending on the way used to create an exception. at creation time: every exception start time is persisted as occurence.startTime in UTC at modification time: every exception start time is persisted as occurence.midnightTime in UTC Exemple , in the database you can see exceptions of a daily recurrent event starting each 18h30 UTC+2: eventexception_parent_id eventexception_child_id eventexception_date 109282   2014-09-14 16:30:00 exception created at event creation time by obm-ui (exception day 2014-09-14) 109282   2014-09-10 22:00:00 exception created on already existing event by obm-ui (exception day 2014-09-11) Problem , obm-ui has two differents behaviors but it must have only one. Then opush and thunderbird must have the same behavior than obm-ui. I guess that the excepted behavior is to not set the exception date at midnight!
          Hide
          Jenkins Continuous Integration Server added a comment -

          SUCCESS: Integrated in poll-qa-25 339-7dfe1968f775d9d651dd190801603589e861b517
          OBMFULL-5922 revert OBMFULL-4703 ( CR-2854 and CR-2870) (jkornobis: 7dfe1968f775d9d651dd190801603589e861b517)

          • java/sync/opush/push-module/src/test/java/org/obm/push/calendar/MSEventToObmEventConverterRecurrenceTest.java
          • java/sync/opush/push-service/src/main/java/org/obm/push/calendar/MSEventToObmEventConverterImpl.java
          • java/sync/opush/push-module/src/test/java/org/obm/push/calendar/MSEventToObmEventConverterExceptionTest.java
          • java/sync/opush/push-module/src/test/java/org/obm/push/calendar/MSEventToObmEventConverterTest.java
          Show
          Jenkins Continuous Integration Server added a comment - SUCCESS: Integrated in poll-qa-25 339-7dfe1968f775d9d651dd190801603589e861b517 OBMFULL-5922 revert OBMFULL-4703 ( CR-2854 and CR-2870) (jkornobis: 7dfe1968f775d9d651dd190801603589e861b517 ) java/sync/opush/push-module/src/test/java/org/obm/push/calendar/MSEventToObmEventConverterRecurrenceTest.java java/sync/opush/push-service/src/main/java/org/obm/push/calendar/MSEventToObmEventConverterImpl.java java/sync/opush/push-module/src/test/java/org/obm/push/calendar/MSEventToObmEventConverterExceptionTest.java java/sync/opush/push-module/src/test/java/org/obm/push/calendar/MSEventToObmEventConverterTest.java
          Hide
          Stephane COLSON added a comment -

          Seems OK with version 2.5.8-0.alpha0+git20140916_1743_b83fdf6 but without clear and precise reproduction steps, we cannot be sure that there is not still any non working behavior.
          I tested OBMFULL-5304, OBMFULL-4703 and with obm 2.5.8-0.alpha0+git20140916_1743_b83fdf6 on CentOS:

          • daily recurrent not-allday event, modified by ui (created, delete exception, move exception, delete recurrence...) and checked on TB24, ipad, Fairphone FP1 Android 4.2.2, Samsung Galaxy SII Android 2.3.3, Windows Phone 8
          • allday weekly recurent event, modified by ui (created, delete exception, move exception, delete recurrence...) and checked on TB24, ipad, Fairphone FP1 Android 4.2.2, Samsung Galaxy SII Android 2.3.3, Windows Phone 8: See new OBMFULL-6115, OBMFULL-6116
          • daily recurrent allday event, modified with TB24 (created, delete exception, move exception, delete recurrence...) and checked on ui, ipad, Fairphone FP1 Android 4.2.2, Samsung Galaxy SII Android 2.3.3, Windows Phone 8: See new OBMFULL-6115, OBMFULL-6116
          • daily recurrent not-allday event, modified with TB24 (created, delete exception, move exception, delete recurrence...) and checked on ui, ipad, Fairphone FP1 Android 4.2.2, Samsung Galaxy SII Android 2.3.3, Windows Phone 8: See new OBMFULL-6115
          • daily recurrent allday event, modified with ipad (created, delete exception, move exception, delete recurrence...) and checked on ui, TB24, Fairphone FP1 Android 4.2.2, Samsung Galaxy SII Android 2.3.3, Windows Phone 8
          • daily recurrent allday event, modified with Fairphone FP1 (created, delete exception, move exception, delete recurrence...) and checked on ui, TB24, ipad, Android 4.2.2, Samsung Galaxy SII Android 2.3.3, Windows Phone 8
          Show
          Stephane COLSON added a comment - Seems OK with version 2.5.8-0.alpha0+git20140916_1743_b83fdf6 but without clear and precise reproduction steps, we cannot be sure that there is not still any non working behavior. I tested OBMFULL-5304 , OBMFULL-4703 and with obm 2.5.8-0.alpha0+git20140916_1743_b83fdf6 on CentOS: daily recurrent not-allday event, modified by ui (created, delete exception, move exception, delete recurrence...) and checked on TB24, ipad, Fairphone FP1 Android 4.2.2, Samsung Galaxy SII Android 2.3.3, Windows Phone 8 allday weekly recurent event, modified by ui (created, delete exception, move exception, delete recurrence...) and checked on TB24, ipad, Fairphone FP1 Android 4.2.2, Samsung Galaxy SII Android 2.3.3, Windows Phone 8: See new OBMFULL-6115 , OBMFULL-6116 daily recurrent allday event, modified with TB24 (created, delete exception, move exception, delete recurrence...) and checked on ui, ipad, Fairphone FP1 Android 4.2.2, Samsung Galaxy SII Android 2.3.3, Windows Phone 8: See new OBMFULL-6115 , OBMFULL-6116 daily recurrent not-allday event, modified with TB24 (created, delete exception, move exception, delete recurrence...) and checked on ui, ipad, Fairphone FP1 Android 4.2.2, Samsung Galaxy SII Android 2.3.3, Windows Phone 8: See new OBMFULL-6115 daily recurrent allday event, modified with ipad (created, delete exception, move exception, delete recurrence...) and checked on ui, TB24, Fairphone FP1 Android 4.2.2, Samsung Galaxy SII Android 2.3.3, Windows Phone 8 daily recurrent allday event, modified with Fairphone FP1 (created, delete exception, move exception, delete recurrence...) and checked on ui, TB24, ipad, Android 4.2.2, Samsung Galaxy SII Android 2.3.3, Windows Phone 8
          Hide
          Jenkins Continuous Integration Server added a comment -

          SUCCESS: Integrated in poll-next-30 574-27d7c252df8c018e78d651b8499c155f690f7cae
          OBMFULL-5922 Good date and time format for removed exception (jkornobis: 27d7c252df8c018e78d651b8499c155f690f7cae)

          • ui/php/calendar/calendar_index.php
          Show
          Jenkins Continuous Integration Server added a comment - SUCCESS: Integrated in poll-next-30 574-27d7c252df8c018e78d651b8499c155f690f7cae OBMFULL-5922 Good date and time format for removed exception (jkornobis: 27d7c252df8c018e78d651b8499c155f690f7cae ) ui/php/calendar/calendar_index.php
          Hide
          Jenkins Continuous Integration Server added a comment -

          FAILURE: Integrated in poll-master-31 42-937f529a0e51f50ef9d93e46c4a340b6ebe0ad71
          OBMFULL-5922 Good date and time format for removed exception (ddolcimascolo: ecc30efeb6c8c294106b1901c53b65c1315cbb65)

          • ui/php/calendar/calendar_index.php
          Show
          Jenkins Continuous Integration Server added a comment - FAILURE: Integrated in poll-master-31 42-937f529a0e51f50ef9d93e46c4a340b6ebe0ad71 OBMFULL-5922 Good date and time format for removed exception (ddolcimascolo: ecc30efeb6c8c294106b1901c53b65c1315cbb65 ) ui/php/calendar/calendar_index.php

            People

            • Assignee:
              jeremie kornobis
              Reporter:
              David Dolcimascolo
            • Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: