C.1 error in process filter: HTTP Error: 502, "Bad gateway" ¶

This is a frequently occurring error. Adding some formatting, the full error is:

error in process filter: ghub--signal-error: HTTP Error: 502,
  "Bad gateway", "/graphql",
  ((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 `CC2C:4FEA:A1771C1:CBF40CE:5C33F7E5`
      when reporting this issue."))))

This indicates that something went wrong within Github’s network. Unfortunately the reason given is rather vague, but I believe this usually happens when there are topics with one or two magnitudes more posts than usual, which can cause GraphQL responses to become huge.

This can be countered in the affected repository by setting the Git variable forge.graphqlItemLimit:

git config --local forge.graphqlItemLimit 20

The default is specified using the ghub-graphql-items-per-request, which defaults to 50 (down from Github’s default and maximum of 100).

Fetching less items per request results in more requests, which slows down the process, which is why the default should not be too small, but for some repositories a more aggressive limit is needed.