repository does not exist
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start at the src search --json entry point and trace handling of GraphQL errors at search.results.results[].file.content. Use the provided query as a starting point, though reproduction requires the reporter's corporate data. Done means a missing repository does not fail the entire search and the remaining results are still handled consistently.
Written by the indexing model from the issue text.
Description
When I perform a search like
src search --json "repo:has.file(package.json) file:package.json "some-package" count:1000"
The whole search fails for a repo that "does not exist"
GraphQL errors: {
"message": "repository does not exist: repo-name",
"path": [
"search",
"results",
"results",
309,
"file",
"content"
]
The query works with a small count before it hits an error. Is there a way for the cli to skip GraphQL errors? The query works fine within the sourcegraph webapp.
I cannot give a case to reproduce because this depends on our corporate data
- Dominant language
- Go
- Stars
- 356
- Forks
- 76
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 13
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from sourcegraph/src-cli
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
sourcegraph/src-cli#1345 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
sourcegraph/src-cli#1144 · 3 comments ·
-
good first issue ux
Difficulty 4/5 3-5 days Newbie friendliness 45/100
sourcegraph/src-cli#930 · 1 comment ·
All issues in sourcegraph/src-cli
Similar issues
-
textual definition
Difficulty 1/5 Under an hour Newbie friendliness 90/100
geneontology/go-ontology#32653 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
needs design
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Priority/High ready-for-agent Severity/Major Type/Bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100