Can't use Github panel for a private repo inside my company - "Query errors reported: could not resolve 'name'"

[jpvalery]

Description

I'm facing an annoying (but tolerable) issue with the Github panel. I have been added to the team for my company and a repo created. I've cloned the repo through SSH. I can commit, push, etc... with Atom without issue. However, the Github panel gives me this error:

Things I've investigated I've tried inspecting with the console but didn't get anything. I've tried logging out and back in, to no success.

Expected behavior: Get the usual module

Actual behavior: Error is displayed

Reproduces how often: 100%

Versions

Atom    : 1.36.0
Electron: 2.0.18
Chrome  : 61.0.3163.100
Node    : 8.9.3

apm  2.1.3
npm  6.2.0
node 8.9.3 x64
atom 1.36.0
python 2.7.10
git 2.17.1

Additional Information

I have no issue accessing this repo with Github desktop

[rsese]

Thanks for the report! To clarify, are you only having issues with your company's private repositories and otherwise have no issues with a repository owned by your user account for example?

[jpvalery]

Exactly! Hence my surprise :)

Tried talking with the person in charge of our repos and he had no idea as to why it behaves this way.

Le 24 avr. 2019 à 22:31, Robert Sese [email protected] a écrit :

Thanks for the report! To clarify, are you only having issues with your company's private repositories and otherwise have no issues with a repository owned by your user account for example?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[rsese]

Hmm, though the error message is different, does this apply to your organization?

https://github.com/atom/github/issues/1010#issuecomment-422882361

[jpvalery]

IDK. I shared this with the person responsible for our GitHub and will report back if/when I hear back.

[RinardNick]

This is a problem for me as well, "Query errors reported" Could not resolve to a Repository with the name '******'

[jquinn-antaeus]

I was having a similar issue that was resolved by the repo admin re-sending the invitation to the repo. Once I accepted the invitation, I could see the repository in search results and the repo appeared in the "repositories" sidebar of my github.com main page. Entering the key into Atom connected to GitHub with no further errors.

[rsese]

@jquinn-antaeus were you also seeing the "Query errors reported" Could not resolve to a Repository with the name" error message?

For folks seeing that specific error, do you happen to be using repositories hosted on a GitHub Enterprise instance?

[jquinn-antaeus]

@jquinn-antaeus were you also seeing the "Query errors reported" Could not resolve to a Repository with the name" error message?

Yes. The search for that error led me to this thread.

[rogerkk]

@rsese I see this error, but I'm not using Github Enterprise.

[Si-Thu-Thein]

I also have this error with one of my repos in my organization

[rsese]

Is there anything different about the repository that you can think of versus the rest of the repositories in your organization @Si-Thu-Thein? Do you have the same permissions on this particular repository?

[olbrich]

I am seeing errors like this when trying to look at an 'internal' repository in our corporate organization which is using Github enterprise cloud. I think we also have SSO enabled as I am asked to do that from time to time when using the Github UI.

[Si-Thu-Thein]

@rsese I don't think this repo has any special permissions at all, except that it's a private one. But another private repo is working fine...

[rdpoor]

I'm also now seeing "Query errors reported / Could not resolve to a Repository with the name 'xxxx'" As with the original post, in a MINGW shell window, I can access the repo and fetch, push, etc.

The only relevant change I can think of is that I recently created a ~/.ssh/config file to access a client's atlassian account. But this error is regarding github.

Addendum: FWIW, I also tried logging out from Github and logging in (after generating a new token). No improvement.

[HadrienPatte]

If it helps, I have the Query errors reported: could not resolve 'name' for a private repository in an organization that requires 2FA and I don't have it on private repositories with no 2FA required.

[danbrannon]

I don't have 2FA enabled. I'm getting this error on an organization's private repo .wiki as well.

[FXschwartz]

I am getting this error on my organization's private repo as well! Query errors reported: could not resolve to a repository with the name 'name'

[kkhanh]

Same on my organization

[Ghormdog]

You need your GitHub Admin to go to "Third-Party Access" to approve the access request. Its how we solved this issue on our side.

[FXschwartz]

@Ghormdog I am a GitHub Admin for our organization and there is not even an option under Third-party access for Atom GitHub package. How did you request access through Atom?

[3m-jr]

@Ghormdog I am a GitHub Admin for our organization and there is not even an option under Third-party access for Atom GitHub package. How did you request access through Atom?

@FXschwartz Could this be helpful? I was having similiar issues and followed this:

https://help.github.com/en/github/setting-up-and-managing-your-github-user-account/requesting-organization-approval-for-oauth-apps

[FXschwartz]

@jamesr-3rdmill That did it!

Thank you so much for your help! All is working now.

[Ghormdog]

Thanks all - appreciate it!

On Wed, Jan 15, 2020 at 8:50 AM Preston [email protected] wrote:

@jamesr-3rdmill https://github.com/jamesr-3rdmill That did it!

Thank you so much for your help! All is working now.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/atom/github/issues/2093?email_source=notifications&email_token=AE4TKU7EEW7I532W7O3SJKDQ54IDXA5CNFSM4HIGLYWKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJALZ4A#issuecomment-574668016, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE4TKU43WJ5C6WF7JJKHWY3Q54IDXANCNFSM4HIGLYWA .

[ivo-ivanov]

@Ghormdog thank you, this solved my issue!

[billhofmann-fade]

Nope, not working in 1.51.0. Query errors reported, Could not resolve to a Repository with name '/'. Console reports uncaught throw: Uncaught (in promise) Error: GraphQL API endpoint at https://api.github.com/graphql returned an error for query GetMentionableUsers. at fetchQuery (/Applications/Atom.app/Contents/Resources/app/static/:14) at UserStore.loadMentionableUsers (/Applications/Atom.app/Contents/Resources/app/static/:14) at async Promise.all (index 0) at UserStore.loadUsers (/Applications/Atom.app/Contents/Resources/app/static/:14)

[Errorbot1122]

has anyone found an answer to this issue?

[bstivers]

The above third-party access worked for me with some slight menu tweaks. Make sure it's approved on the organization side as well as your own profile side. For more info, see here:

https://docs.github.com/en/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions