Persistent 502 when querying

This query returns, consistently, 502 Bad Gateway, which is unexpected imo because it’s retrieving a small amount of data (10k nodes << 500k NodeLimit)

{
  organization(login: "github") {
    login
    repositories(first: 100) {
      nodes {
        name
        pullRequests(first: 100) {
          nodes {
            title
          }
        }
      }
    }
  }
}

502 Bad Gateway
{
   "data": null,
   "errors":[{
      "message":"Something went wrong while executing your query. This may be the result of a timeout, or it could be a GitHub bug. Please include `CB9E:2FD5B:2576F3:2E3E99:5D9F432B` when reporting this issue."
   }]
}

I tried with some other orgs, and it failed the same way.

I also tried with ever fewer nodes, and also failed (50 repos and 30 PRs -> 1.5k <<< 500k NodeLimit)

Isn’t the current NodeLimit of 500k, something in what we can trust?

2 Likes

Are you still receiving this error? I tried the query you supplied and it worked for me, but I have access to the github organization, so it isn’t exactly an apples-to-apples comparison.

Let us know and we’ll take another look.

I tried with the query from my message above, —which was beeing failing for days—, and the error disappeared.

But I’m still having the very same error with this similar query, which is still way below the limits

(2k nodes << 500k NodeLimit)

{
  organization(login: "github") {
    login
    repositories(first: 100) {
      nodes {
        name
        pullRequests(first: 100) {
          nodes {
            title
            labels(first: 1) {
              nodes {
                name
              }
            }
          }
        }
      }
    }
  }
}

{
   "data": null,
   "errors":[
      {
         "message":"Something went wrong while executing your query. This may be the result of a timeout, or it could be a GitHub bug. Please include `DD1C:1619D:2C2072:35EA1B:5DB1AF93` when reporting this issue."
      }
   ]
}

The err code that is now returned is:

DD1C:1619D:2C2072:35EA1B:5DB1AF93

Does it make sense to you that this error is happening from time to time?

1 Like

Yes, it does make sense. I was able to reproduce the error and it is a timeout. Even with the node limit, there is a maximum query time that can limit the size of queries as well. If you’re getting this error, try requesting less data to see if the query works on a technical level or if it still errors out.

Let us know if you have more questions.

1 Like