Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
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
- NOK deletions are not took in account by the device, even by forcing new syncs
Expected behavior
- 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
| Field | Original Value | New Value |
|---|---|---|
| Attachment | notDeletedEmail [ 14516 ] |
| Sprint | 2016#01 [ 30 ] |
| Story Points | 2 |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | Stopped [ 10000 ] |
| Status | Stopped [ 10000 ] | Open [ 1 ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| 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/ |
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/ |
| Story Points | 2 | 6 |
| Status | In Progress [ 3 ] | In Review [ 10001 ] |
| Status | In Review [ 10001 ] | Ready To Merge [ 10002 ] |
| Resolution | Fixed [ 1 ] |
| Status | Ready To Merge [ 10002 ] | Resolved [ 5 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |