Closed
Bug 632436
Opened 15 years ago
Closed 12 years ago
"Query has timed out." when searching Firefox beta with empty/inclusive start/end dates
Categories
(Input :: General, defect, P1)
Input
General
Tracking
(Not tracked)
RESOLVED
WORKSFORME
Future
People
(Reporter: stephend, Unassigned)
References
()
Details
(Whiteboard: [fromAutomation][stage])
http://input.stage.mozilla.com/en-US/beta/search?product=firefox&version=--&date_start=&date_end is throwing a "Search unavailable" error:
"Query has timed out."
Comment 1•15 years ago
|
||
We should block the release for now.
Bugs like this on launch day are bad. I can probably fix these today or tomorrow. I'm kind of in a black hole stuck inside a cave here, without a flashlight... in regards to this bug.
Updated•15 years ago
|
Assignee: nobody → dd
Comment 2•15 years ago
|
||
http://github.com/fwenzel/reporter/commit/1e5ca57
Fixed, sorting was too slow... I suspect we might have more issues so I still stand by my let's delay this release and QA the **** out of this.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 3•15 years ago
|
||
Sadly, still happening; maybe need to do something with IT to get this resolved/updated?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 4•15 years ago
|
||
Bumping this - I think this is ultimately a sphinx limitation/configuration issue.
This may change when we get our own staging hardware for Sphinx. Bumping for now.
When we're looking at less than 1M documents we should be okay, so it shouldn't be too bad.
Downgrading from critical - no data loss/corruption, just loss of functionality
Severity: critical → major
Target Milestone: 3.1 → 3.3
Updated•15 years ago
|
Priority: -- → P1
Updated•14 years ago
|
Flags: in-testsuite+
Comment 7•14 years ago
|
||
sigh
http://github.com/fwenzel/reporter/commit/82a5915
So the way it works is you see about 60 days back.
Comment 8•14 years ago
|
||
Automation has been re-enabled and is passing. All green again. QA verified.
Status: REOPENED → RESOLVED
Closed: 15 years ago → 14 years ago
Resolution: --- → FIXED
Comment 9•14 years ago
|
||
I still get the "Query has timed out." message.
Via what URL?
Comment 11•14 years ago
|
||
I see this on selecting version as All from the beta input dashboard. The URL that I get is http://input.mozilla.com/en-US/beta/search?product=firefox&version=--&date_start=&date_end=
Comment 12•14 years ago
|
||
sdrocking ~ good find however that is our production environment. Checkout the latest fix on stage at http://input.stage.mozilla.com/en-US/beta/search?product=firefox&version=--&date_start=&date_end
see comment 1
Comment 15•14 years ago
|
||
I'm gonna close this one since both manual & automated tests (re-enabled last week) are all passing.
QA verified.
Status: RESOLVED → VERIFIED
Comment 16•14 years ago
|
||
Sorry to reopen this yet again. It has begun happening consistently on stage again. Our automation caught and alerted us to it.
http://input.stage.mozilla.com/en-US/beta/search?product=firefox&version=--&date_start=&date_end=
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Whiteboard: [fromAutomation] → [fromAutomation] [stage]
Comment 17•14 years ago
|
||
(In reply to comment #17)
> http://qa-selenium.mv.mozilla.com:8080/job/input%20stage/435/artifact/input.stage.mozilla.com_1299780246.png
This is just a screenshot of the Query Timeout for those of you not in MV or on the office VPN.
So yes, we're aware of what the error looks like - there is a dependent bug for IT - other than that we're stuck unless we want to further cripple the product.
Comment 19•14 years ago
|
||
Deferring this one to 3.4. I don't like how this keeps reappearing, but it (luckily) doesn't impact the front page, so I am not going to delay tonight's push about it.
That being said, as Dave noted, this is a high priority because it'll get worse as data grows.
Target Milestone: 3.3 → 3.4
Updated•14 years ago
|
Whiteboard: [fromAutomation] [stage] → [fromAutomation][stage][3.5]
Updated•14 years ago
|
Whiteboard: [fromAutomation][stage][3.5] → [fromAutomation][stage]
Target Milestone: 3.4 → 3.5
This requires ElasticSearch which won't be in place until after this iteration, bumping to 4.0
Target Milestone: 3.5 → 4.0
Favoring API over this for now, and I don't want to do more than one big thing per release.
Target Milestone: 4.0 → 4.1
Moving things dependent on ES to FUTURE.
Depends on: 627568
Target Milestone: 4.1 → Future
Reporter | ||
Comment 23•14 years ago
|
||
Happy to report that, post-fix bug 627568, http://input.allizom.org/en-US/search?product=firefox&version=--&date_start=&date_end is working fine again.
(In reply to comment #23)
> Happy to report that, post-fix bug 627568,
> http://input.allizom.org/en-US/search?product=firefox&version=--
> &date_start=&date_end is working fine again.
Lol, I think that's because not everything is being shown :)
Assignee | ||
Updated•14 years ago
|
Component: Input → General
Product: Webtools → Input
Updated•14 years ago
|
Assignee: dd → nobody
Comment 25•12 years ago
|
||
This isn't an issue anymore with the new Input. Marking as WORKSFORME.
Status: REOPENED → RESOLVED
Closed: 14 years ago → 12 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•