Closed
Bug 512906
Opened 16 years ago
Closed 16 years ago
backoff not triggered by engine errors
Categories
(Firefox :: Sync, defect, P1)
Firefox
Sync
Tracking
()
RESOLVED
FIXED
0.7
People
(Reporter: mconnor, Assigned: mconnor)
References
Details
We should definitely fix this for beta.
Flags: blocking-weave1.0+
Comment 1•16 years ago
|
||
I think it's because the engine failure is eaten up and the overall service:sync doesn't trigger error.
Assignee | ||
Comment 2•16 years ago
|
||
Nope, weave:service:sync:error shows in the logs, but since we don't have a failure state on detailedStatus.sync, we don't know it's a server error, not a client error, and we don't back off.
Updated•16 years ago
|
Priority: -- → P1
Updated•16 years ago
|
Priority: P1 → P2
Updated•16 years ago
|
Priority: P2 → P1
Assignee | ||
Comment 3•16 years ago
|
||
fixed by bug 511549
Updated•7 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
•