Closed Bug 482611 Opened 17 years ago Closed 17 years ago

After update that requires server wipe second client uploads all data to server again

Categories

(Cloud Services :: General, defect)

x86
Windows Vista
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: timeros, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b3) Gecko/20090305 Firefox/3.1b3 (.NET CLR 3.5.30729) Build Identifier: 0.2.111 After the first client wipes the server and uploads all items to he server. The second client detects the wipe, clears local cache but again does a full upload of items to the server Reproducible: Always Steps to Reproduce: 1. Upgrade Computer1 2. Computer1 does a server wipe and upload of all items (OK) 3. Upgrade Computer2 4. Computer2 detects server wipe, clears local caches and again makes upload of all items Actual Results: Computer2 does a second full upload (and thus could override some data from Computer1) Expected Results: Copmuter2 should just download the data from the server, reconcile it and upload only records that are changed on Computer2
I can't reproduce this. For me, the second client does reconcile data: 2009-03-10 16:15:32 Engine.Bookmarks INFO 737 outgoing items pre-reconciliation 2009-03-10 16:16:32 Engine.Bookmarks INFO Applied 7 records, reconciled 737 records 2009-03-10 16:16:32 Engine.Bookmarks INFO Uploading 1 records + 200 index/depth records) closing as worksforme.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
Target Milestone: -- → 0.3
My mistake. On the second computer i saw "First sync, uploading all items" and i thought it was doing a full upload. Looking it in more details i see that it reconcile the changes from the server.
Ah, yes. The local metadata reset causes the client to do that. It really means it will _consider_ all items for upload (as opposed to in a regular sync, Weave only considers added/changed/removed items).
Component: Weave → General
Product: Mozilla Labs → Weave
QA Contact: weave → general
You need to log in before you can comment on or make changes to this bug.