Open NickBarnes opened 9 months ago
That used to happen quite frequently, so there is a FAQ entry about it. (Well about 502, but what I've written about that, should also apply to 504.)
Looking at that, I realized that it needs updating. We now know a bit more what is causing it (well at least one cause). The fix/workaround is mentioned at https://github.com/magit/forge/issues/20#issuecomment-1481646089.
That workaround (git config --local forge.graphqlItemLimit 50
) changes my 504 to a 502. Various other numbers (20, 10) don't fix it.
I'll delay looking into this until after the current round of major changes to Forge (i.e., until after the next release).
Trying to get started with forge. I got as far as my first forge-pull and hit:
I set
forge.omitExpensive
totrue
as suggested by theforge-pull
docstring, but that doesn't change the error. Here's the backtrace: