Closed Bug 504373 Opened 15 years ago Closed 15 years ago

Be smarter in detecting when it's safe to sync after a wipe

Categories

(Firefox :: Sync, defect, P3)

Product:
Firefox
Component:
Sync
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Milestone:
1.0 beta3

People

(Reporter: Mardak, Unassigned)

References

Details

Until bug 504125 is fixed, a temporary fix was needed with bug 504372 to just sleep a little after wiping.

We can be smarter by requesting the data and seeing if it's empty before continuing.
Priority: -- → P2
Target Milestone: --- → 0.7
Priority: P2 → P3
Flags: blocking-weave1.0+
Target Milestone: 0.7 → 0.8
moving beta blockers to block 1.0 beta
Target Milestone: 0.8 → 1.0 beta
Target Milestone: 1.0beta → 1.0
If bug 526084 is fixed, there shouldn't be an issue with replication lag, so this wouldn't need to be fixed.
Target Milestone: 1.0 → 1.0 beta2
Actually we're already running 1.0 reading from the master, so replication lag won't affect 1.0 clients.

There's more to do in bug 526084, but the portions of it that this bug depends on can be considered FIXED.

Your call if you want to leave this open until the rest of that bug is done.
I think this is as fixed as it needs to be.  Thanks Zandr!
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
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.