-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Global search on Sourcegraph.com should indicate that repo: filter is needed #3966
Comments
@nicksnyder changed the default searchable number of repos to be unlimited, and sourcegraph.com appears to be using the default. Instead of an error, I think we could show some repo results that could then be used to refine the query. Watch count could be a useful indicator of relevance. Here's a bigquery showing what that looks like for "vim": |
To be clear, I'm not necessarily saying we should use bigquery for this. It just happens to have a dataset that helps to see what would happen with a simple approach like this. One possibility that could work not just on github would be to periodically query the |
To give a rough idea of what that could look like, here's some data from the
where the |
Of course we'd have to join |
Streaming (#3991) should make it unnecessary to require a repo: filter on sourcegraph.com since some results would show up pretty quickly in many cases and all of them would eventually show up at least for the repos that are currently cloned. |
I have set This is fixed now, so closing. |
@slimsag Imo this issue is not resolved. A private instance can still configure a higher number and run into the "Context deadline exceeded" error instead of the expected alert. |
@felixfbecker point taken, However, the correct behavior in this case would be telling the user that they need to increase the |
I would rather go with the cursor based solution we've been chatting about.
Then we won't have to rely so heavily on these less reliable timeouts and
max repo settings.
…On Tue, May 21, 2019, 5:08 PM Stephen Gutekanst ***@***.***> wrote:
@felixfbecker <https://github.com/felixfbecker> point taken, Context
deadline exceeded is not a helpful message and we should fix that.
However, the correct behavior in this case would be telling the user that
they need to increase the timeout parameter. If I say I want my instance
to be able to search over 1000 repositories and that's too slow, I don't
expect it to tell me to specify a repo: filter.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#3966?email_source=notifications&email_token=AAADZKVDD2I2DNATTX2BZ3TPWSFIZA5CNFSM4HML3RF2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV5Q4CA#issuecomment-494603784>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAADZKWTGHPXGUMMDO73LVLPWSFIZANCNFSM4HML3RFQ>
.
|
@slimsag took care of this specific issue. Closing it. |
@felixfbecker, there should be a separate issue about the point you raised if we're able to reproduce it. |
Global search isn't supported on Sourcegraph.com. If the user specifies a query that exceeds the maximum number of allowed repositories to search over (implemented in the code link below), they should see a helpful message instead of just a "context deadline exceeded" error.
Repro:
Actual:
Expected: The "Too many matching repositories" alert at https://sourcegraph.com/github.com/sourcegraph/sourcegraph@6f954bbc1cfc4a54d715f42325cb2ea4037e93ec/-/blob/cmd/frontend/graphqlbackend/search_alert.go#L222:11
(From https://twitter.com/sqs/status/1127746584811192320)
The text was updated successfully, but these errors were encountered: