Closed
Bug 556138
Opened 16 years ago
Closed 16 years ago
Set timeout to 1 second and catch any socket errors when talking to sphinx
Categories
(addons.mozilla.org Graveyard :: Search, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
5.9
People
(Reporter: jbalogh, Assigned: davedash)
Details
(Whiteboard: [z])
oremj suggests the 1 second timeout. It works for me.
We catch the timeout error during connect, but those could happen at any time. We also had Connection reset by peer errors today. Sphinx doesn't catch any of these. We should throw a wide net when talking to Sphinx.
| Assignee | ||
Updated•16 years ago
|
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 1•16 years ago
|
||
2b48d38c92d8b71b80eedde192c819de0a609edf
| Reporter | ||
Comment 2•16 years ago
|
||
http://github.com/jbalogh/zamboni/commit/2b48d38c fixes the timeout, but we still need to catch more exceptions.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 3•16 years ago
|
||
Is this fixed with http://github.com/jbalogh/zamboni/commit/81e0a3bbdb68dd700abd111c81161fb8c00c9712 from 5.8.3?
| Reporter | ||
Updated•16 years ago
|
Status: REOPENED → RESOLVED
Closed: 16 years ago → 16 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•