Opush
  1. Opush
  2. OP-231

Some changes can be missed when a device use twice the same synckey

    Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Normal Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.2.0
    • Labels:
      None
    • Story Points:
      6
    • Rank:
      6964
    • Sprint:
      2016#01

      Description

      Some changes can be missed when a device use twice the same synckey

      Reproduction steps

      None, this can be hard to reproduce but you can try these steps:

      • synchronize usera emails with a device
      • cut the device network
      • send to usera a bunch of 1000 emails
      • reconnect the device network
      • as soon as it starts to make a request (see logs), cut the network again
      • reconnect the device network
      • let the device synchronize a bunch of new emails (~100 emails)
      • make some changes with another MUA (tb, roundcube, ..) like deletions or read status updates

      Current behavior

      1. NOK deletions are not took in account by the device, even by forcing new syncs

      Expected behavior

      1. OK deletions are took in account by the device, may be that you will need to force new syncs

      Note:
      I've written tests for this jira, I've also tried a fix but we should evaluate another way to make that. See thilaire/OP-231

        Activity

        Thomas HILAIRE made changes -
        Field Original Value New Value
        Attachment notDeletedEmail [ 14516 ]
        David Dolcimascolo made changes -
        Sprint 2016#01 [ 30 ]
        David Dolcimascolo made changes -
        Story Points 2
        Thomas HILAIRE made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        Thomas HILAIRE made changes -
        Status In Progress [ 3 ] Stopped [ 10000 ]
        Thomas HILAIRE made changes -
        Status Stopped [ 10000 ] Open [ 1 ]
        Thomas HILAIRE made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        Thomas HILAIRE made changes -
        Description Some changes can be missed when a device use twice the same synckey

        *Reproduction steps*:
        {color:red}None{color}, this is a really hard to reproduce issue as:
        - the server must be long to reply, to make the device retrying with the same sync-key, in a windowing
        - some changes must be triggered during this small lapse of time

        *Note*:
        I've written tests for this jira, I've also tried a fix but we should evaluate another way to make that. See thilaire/OP-231
        Some changes can be missed when a device use twice the same synckey

        h4. Reproduction steps
        {color:red}None{color}, this can be hard to reproduce but you can try these steps:
        - synchronize _usera_ emails with a device
        - cut the device network
        - send to _usera_ a bunch of 1000 emails
        - reconnect the device network
        - as soon as it starts to make a request (see logs), cut the network again
        - reconnect the device network
        - let the device synchronize a bunch of new emails (~100 emails)
        - make some changes with another MUA (tb, roundcube, ..) like deletions or read status updates

        h4. Current behavior
        # {color:red}NOK{color} deletions are not took in account by the device, even by forcing new syncs

        h4. Expected behavior
        # {color:green}OK{color} deletions are took in account by the device, may be that you will need to force new syncs

        *Note*:
        I've written tests for this jira, I've also tried a fix but we should evaluate another way to make that. See thilaire/OP-231
        Thomas HILAIRE made changes -
        Story Points 2 6
        Thomas HILAIRE made changes -
        Status In Progress [ 3 ] In Review [ 10001 ]
        Thomas HILAIRE made changes -
        Status In Review [ 10001 ] Ready To Merge [ 10002 ]
        Resolution Fixed [ 1 ]
        Thomas HILAIRE made changes -
        Status Ready To Merge [ 10002 ] Resolved [ 5 ]
        Stephane COLSON made changes -
        Status Resolved [ 5 ] Closed [ 6 ]

          People

          • Assignee:
            Thomas HILAIRE
            Reporter:
            Thomas HILAIRE
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Agile