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

[BUG] Timeout in the GraphQL API in private organizations (many repositories, with SSO enabled) #242

Open
wnqueiroz opened this issue Mar 8, 2023 · 3 comments
Labels
bug Something isn't working

Comments

@wnqueiroz
Copy link

wnqueiroz commented Mar 8, 2023

Describe the bug

Hello Folks!

I installed the extension (without doing much configuration) and when running the gh dash command I get the following error message:

Post "https://api.github.com/graphql": dial tcp: lookup api.github.com: i/o timeout

Analyzing the source, I found no way to configure authentication settings for the GraphQL API...

Looking at the library that is used to access the GitHub API (https://github.com/cli/shurcooL-graphql), there is a setting to define the API access token (in the GRAPHQL_TOKEN environment environment variable) but I believe that it is not used throughout the project and no GraphQL client is created...

Am I doing something wrong? Does anyone else have this problem?

To Reproduce

I don't know how to best describe my environment, but here it is:

  • Private organization (with private repositories);
  • SSO enabled.

I'm just running the gh dash command from a private project and getting the timeout...

💡 The organization has more than 3k repositories... I don't know if the timeout problem is related to the actual authentication or just due to a large data fetch.

Expected behavior

Be able to view the dashboard by accessing private organization data (which uses SSO as authorization).

Screenshots

image

Desktop (please complete the following information):

  • OS: MacOSX Ventura 13.0.1
@wnqueiroz wnqueiroz added the bug Something isn't working label Mar 8, 2023
@wnqueiroz
Copy link
Author

cc @diego3g

@dlvhdr
Copy link
Owner

dlvhdr commented Mar 8, 2023

Hello!

Maybe you need to run gh auth login

@wnqueiroz
Copy link
Author

Hello!

Maybe you need to run gh auth login

@dlvhdr I thought it was something with the gh CLI authentication but I'm already authenticated...

image

I have 2 signs of what might be going on:

  • Authentication required by GitHub's GraphQL server (as it is a private organization); or
  • Timeout by the amount of repositories in the organization (as I mentioned, it's +3k 😅)

This second case is more difficult to reproduce... Does it make sense for you? If it's in the way, I'll try to implement something to solve the problem.

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

No branches or pull requests

2 participants