Closed Bug 1224203 Opened 9 years ago Closed 9 years ago

Detecting Server Unreachable takes several minutes

Categories

(Firefox OS Graveyard :: Sync, defect)

Product:
Firefox OS Graveyard
Component:
Sync
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED
Milestone:
2.6 S2 - 12/4

People

(Reporter: mbdejong, Assigned: mbdejong)

References

Details

Attachments

(3 files)

[gaia] michielbdejong:1224203-network-timeouts > mozilla-b2g:master
46 bytes, text/x-github-pull-request
ferjm
: review+
Details | Review
[gaia] michielbdejong:1224203-set-network-timeout > mozilla-b2g:master
46 bytes, text/x-github-pull-request
Details | Review
[gaia] ferjm:bug1224203.followup > mozilla-b2g:master
46 bytes, text/x-github-pull-request
Details | Review
No description provided.
If you set '123.123.123.123 syncto.dev.mozaws.net' in /etc/hosts and click 'Sync Now' in B2G Sync settings, it takes about 4 minutes and 40 seconds before it times out. That's too long. :)
Should test with https://github.com/Kinto/kinto.js/pull/264 - might well be the fix for this! :)
Assignee: nobody → mbdejong
Blocks: fxos-sync
Target Milestone: --- → 2.6 S1 - 11/20
Target Milestone: 2.6 S1 - 11/20 → 2.6 S2 - 12/4
Attachment #8691994 - Flags: review?(ferjmoreno)
Comment on attachment 8691994 [details] [review] [gaia] michielbdejong:1224203-network-timeouts > mozilla-b2g:master You need to rebase
Attachment #8691994 - Flags: review?(ferjmoreno) → review+
Thanks! Rebased.
Flags: needinfo?(ferjmoreno)
https://github.com/mozilla-b2g/gaia/commit/4be1be611fedb425b09aea0661faba0ff86eb704
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(ferjmoreno)
Resolution: --- → FIXED
I had to revert this commit cause the timeout policy was too strict https://github.com/mozilla-b2g/gaia/commit/73ec13faf558bc2531a81ee2302f01a785795ef7
Status: RESOLVED → REOPENED
Flags: needinfo?(mbdejong)
Resolution: FIXED → ---
The reason we had to revert this is that we left the timeout value at the 5 seconds default from Kinto.js, which is not realistic on mobile. I will set the timeout to 180 seconds instead of 5 seconds, then it should be safe again.
Flags: needinfo?(mbdejong)
I've just sent an alternative PR to fix the linter error. Needing info me to remember to merge this tomorrow, once treeherder is done.
Flags: needinfo?(ferjmoreno)
https://github.com/mozilla-b2g/gaia/commit/33c3fd4028a5d4b6aa67aade46a48b505f295162
Status: REOPENED → RESOLVED
Closed: 9 years ago → 9 years ago
Flags: needinfo?(ferjmoreno)
Resolution: --- → FIXED
Blocks: 1234172
Follow-up for v2.5 branch is bug 1235762.
Blocks: 1235762
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: