Skip to content
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

Repository Query does not match search #869

Open
Piszmog opened this issue Oct 18, 2022 · 3 comments
Open

Repository Query does not match search #869

Piszmog opened this issue Oct 18, 2022 · 3 comments
Labels
bug Something isn't working team/code-search

Comments

@Piszmog
Copy link
Contributor

Piszmog commented Oct 18, 2022

When running locally (preview & apply), the number of repositories returned does not match search. For example when count is set to 65, only 64 repos are found. Higher counts like 400 return 397 repos.

When compared to search, search does return the correct number.

src search -- 'repo:^ghe.sgdev.org/testing/.*$ count:65'

Example YAML

on:
- repositoriesMatchingQuery: repo:^ghe.sgdev.org/testing/.*$ count:65

Output

✅ Resolved 64 workspaces from 64 repositories
✅ Found 0 cached changeset specs; 64 tasks need to be executed
✅ Executing... (64/64, 0 errored

Image

Done

  • The number of repositories found should match search

Setup

Use the scaletesting instance to test.

@Piszmog Piszmog changed the title Incorrect workspaces count Repository Query off by one Oct 18, 2022
@Piszmog Piszmog changed the title Repository Query off by one Repository Query does not match search Oct 18, 2022
@Piszmog Piszmog transferred this issue from sourcegraph/src-cli Oct 18, 2022
@Piszmog Piszmog changed the title Repository Query does not match search src-cli: Repository Query does not match search Oct 18, 2022
@Piszmog Piszmog transferred this issue from sourcegraph/sourcegraph Oct 18, 2022
@Piszmog Piszmog changed the title src-cli: Repository Query does not match search Repository Query does not match search Oct 18, 2022
@chrispine
Copy link
Contributor

weird, would be great to figure out what's going on (and if it's that some are hidden for whatever reason, to at least say "some may be hidden bcs X") P1?

@courier-new
Copy link
Contributor

Seems like it might be difficult to estimate this one. Is it worth timeboxing "figuring out what's going on" to 0.5d, in case it turns out we're opening a can of worms?

@chrispine
Copy link
Contributor

let's timebox this to 0.5d investigation and see where to go from there

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working team/code-search
Projects
None yet
Development

No branches or pull requests

4 participants