Page MenuHomePhabricator

Searching shorter terms ("gerrit", "cors") in global Phabricator search leads to upstream request timeout (too many results?)
Open, LowPublicBUG REPORT

Event Timeline

Aklapper changed the task status from Open to Stalled.EditedJul 24 2020, 5:54 PM

@Bugreporter: Please always follow https://www.mediawiki.org/wiki/How_to_report_a_bug and provide clear steps to reproduce. (I assume that you can remember what you were searching for in which field(s), basically. You mention "specific term" but you don't tell anyone the "specific term".) Thanks!

The search term is "gerrit", using the main Phabricator search box.

Bugreporter changed the task status from Stalled to Open.Jul 24 2020, 6:12 PM
Aklapper renamed this task from Unable to search a specific term; upstream request timeout to Searching for "gerrit" in global Phabricator search leads to upstream request timeout.Jul 24 2020, 7:22 PM

Cannot reproduce. When I go to https://phabricator.wikimedia.org/search/query/advanced/ and enter gerrit in the Query field, then I get results at https://phabricator.wikimedia.org/search/query/i7vj09V5IFVu/ (which is a different URL).

When I use the search box in the upper right corner, set the search scope in the dropdown to "All Documents", and enter gerrit, I cannot reproduce either (same query).

@Bugreporter: So your steps must be different somehow.

I can reproduce using by typing "gerrit" in the search box in the top right.

I can also reproduce by typing"gerrit" into the main search box

Thanks everyone for confirming!
I go to https://phabricator.wikimedia.org/ . The search scope in the upper right corner is set to All Documents. I enter gerrit and then the Enter key.

In Firefox 78 with my work account, after a while I get results listed on https://phabricator.wikimedia.org/search/query/7Vf7hiUkXclv/#R
But trying the same in Chromium 81 with my personal account, I can reproduce the problem (HTTP 504 error).

Furthermore, the moment I press the Enter key I get this in the console:

core.pkg.js:1026 Uncaught TypeError: typeahead.updatePlaceHolder is not a function
    at Object._callback (core.pkg.js:1026)
    at Function.pass (core.pkg.js:164)
    at Function._dispatchProxy (core.pkg.js:159)
    at Function.dispatch (core.pkg.js:142)
    at HTMLHtmlElement.JX.__rawEventQueue (init.js:19)

A work account may view a number of restricted things.

But trying the same in Chromium 81 with my personal account, I can reproduce the problem (HTTP 504 error).

I'm on Chrome as well fwiw

so I am able to reproduce this when logged out in both Firefox and Chromium.

medium because it works when logged in. The performance isn't great but it does return results before timing out.

With a single common keyword such as "gerrit" we match a ton of documents and the result set is huge, probably not very useful. I don't think there is a solution to that other than narrowing the search with more words.

With a single common keyword such as "gerrit" we match a ton of documents and the result set is huge, probably not very useful. I don't think there is a solution to that other than narrowing the search with more words.

Could it maybe error more usefully? Some sort of alert saying your request returned too many results please narrow it down?

We lt least need to make the result displayed, so that it will be possible to filter results by project. Usually, I only wants results from only one project, and this will reduce one click.

Aklapper renamed this task from Searching for "gerrit" in global Phabricator search leads to upstream request timeout to Searching for "gerrit" in global Phabricator search leads to upstream request timeout (too many results?).Aug 12 2020, 9:33 AM

We lt least need to make the result displayed, so that it will be possible to filter results by project. Usually, I only wants results from only one project, and this will reduce one click.

FWIW I get results from the linked URL. You could bookmark the global search page. Then you could go there, enter the project(s) and fulltext query, then submit them all at once to avoid the extremely resource-intensive query.

core.pkg.js:1026 Uncaught TypeError: typeahead.updatePlaceHolder is not a function

This seems like a separate / unrelated bug.

mmodell lowered the priority of this task from Medium to Low.

I can reproduce the following error message while logged in:

T258803 exception.png (275×1 px, 13 KB)

This is different to the plain text error message I just reported at T291775.

1234qwer1234qwer4 changed the subtype of this task from "Task" to "Bug Report".Sep 26 2021, 11:24 AM

I get this error reliably when I search for "cors" as well.

Aklapper renamed this task from Searching for "gerrit" in global Phabricator search leads to upstream request timeout (too many results?) to Searching shorter terms ("gerrit", "cors") in global Phabricator search leads to upstream request timeout (too many results?).May 22 2022, 7:05 AM
Aklapper added subscribers: AlexisJazz, Dylsss.

I get this error reliably when I search for "cors" as well.

What an odd coincidence, we searched for the same thing. (T308946) Were you also looking for a CORS related task to find a suitable tag? I ended up using a web search engine. There doesn't seem to be any tag for it, guess you're supposed to use "traffic" or something.

browserling.com phabricator timeout.png (768×1 px, 41 KB)

I get this error reliably when I search for "cors" as well.

What an odd coincidence, we searched for the same thing. (T308946) Were you also looking for a CORS related task to find a suitable tag? I ended up using a web search engine. There doesn't seem to be any tag for it, guess you're supposed to use "traffic" or something.

Funny, yeah I was filing T307391 and checking if the request was already documented.

Still an issue on 2023-11-07; I don't think this is fixable but I'd say the error message should be made clearer for end users, asking to use less broad search criteria, and/or to use the specific application search (example: tasks only) instead of the global search across all and any applications.