This should also fix Bug 760360, which involves syncing on an unreliable network. If the connection is closed while we process downloaded records, the sync fails. We should be more optimistic, because on unreliable networks, a simple retry of the connection should allow us to complete the sync.
mobile triage: blocks, duping tony's bug to here
Comment on attachment 630021 [details] [diff] [review] Patch against m-i [Approval Request Comment] Bug caused by (feature/regressing bug #): User impact if declined: transient network errors cause missed syncs Testing completed (on m-c, etc.): builds m-c and aurora Risk to taking this patch (and alternatives if risky): low, patch is straightforward. String or UUID changes made by this patch: none
Chenxia, how can this be verified? at the very least, i'll retry my STR in bug 760360 from my home network next build.
(In reply to Tony Chung [:tchung] from comment #9) > Chenxia, how can this be verified? at the very least, i'll retry my STR in > bug 760360 from my home network next build. In the general case, you'll need an environment that induces transient network errors. In this specific case, you're looking for an environment like your home network -- one that seems to drop idle connections quite rapidly.
Still on the radar for verification on mozilla-15