Closed
Bug 534218
Opened 15 years ago
Closed 14 years ago
Changing sync direction from outdated clients loses client/server data
Categories
(Firefox :: Sync, defect)
Firefox
Sync
Tracking
()
RESOLVED
FIXED
1.3b1
People
(Reporter: Mardak, Assigned: Mardak)
References
Details
(Keywords: dataloss)
Attachments
(1 file)
2.11 KB,
patch
|
mconnor
:
review+
|
Details | Diff | Splinter Review |
This means a client might clear itself before realizing remoteSetup would have prevented the sync.
Flags: blocking-weave1.0+
Comment 1•15 years ago
|
||
This isn't awesome, but the fix is doesn't seem low-risk, and we haven't had many (any?) problems yet, so moving to 1.1.
Flags: blocking-weave1.1+
Flags: blocking-weave1.0-
Flags: blocking-weave1.0+
Assignee | ||
Updated•14 years ago
|
Target Milestone: 1.0 → 1.1
Updated•14 years ago
|
Assignee: nobody → edilee
Updated•14 years ago
|
Target Milestone: 1.1 → 1.2
Assignee | ||
Updated•14 years ago
|
Assignee: edilee → nobody
Updated•14 years ago
|
Flags: blocking-weave1.2+ → blocking-weave1.2-
Target Milestone: 1.2 → 1.3
Updated•14 years ago
|
Assignee: nobody → edilee
Assignee | ||
Updated•14 years ago
|
Summary: sync calls wipeLocal before remoteSetup → sync calls wipeClient before remoteSetup
Assignee | ||
Updated•14 years ago
|
Summary: sync calls wipeClient before remoteSetup → Changing sync direction from outdated clients loses client/server data
Assignee | ||
Comment 3•14 years ago
|
||
Attachment #439083 -
Flags: review?(mconnor)
Updated•14 years ago
|
Attachment #439083 -
Flags: review?(mconnor) → review+
Assignee | ||
Comment 4•14 years ago
|
||
http://hg.mozilla.org/labs/weave/rev/f6525ff92a62 Check remoteSetup first to determine if we're okay to sync before wiping client/remote. Additionally only wipe enabled engines instead of everything.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•14 years ago
|
Target Milestone: 1.3 → 1.3b1
Updated•6 years ago
|
Component: Firefox Sync: Backend → Sync
Product: Cloud Services → Firefox
You need to log in
before you can comment on or make changes to this bug.
Description
•