Plugins timeout for "huge users"

This is a follow-up of #584

Since each plugin are independant (except for the base one which is required and has been patched in #584), some plugins may still have GitHub API timeouts, reported by the following 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 XXXX:XXXX:XXXXXX:XXXXXX:XXXXXXXX when reporting this issue

This issue will be used to track these faulty plugins and eventually change their queries to make them work for “huge users”

If you encounter this issue on a plugin not listed below, don’t hesitate to post it here (and tell on which user it occurs if it’s not yourself) so it can eventually be patched

---

Plugins:

• base
• reactions -> (this one skips errors but should auto-fix itself when graphql api won’t fail for issues endpoints)
• followup -> (should be fixed with refacto of this plugin which also added indepth in #627)
• isocalendar

[lowlighter]

Nice, thanks a lot for reaching them and let us know that they’ll eventually work on it!

[lowlighter]

I ask GitHub support for help on this issue. Here is the reply:

Yeah, as the message indicated – you hit a timeout there. The API has a timeout on processing requests and if that timeout is hit, the request is terminated and you get back an error. Currently, the timeout is 10 seconds. This normally happens when your query involves too much data, so the way to avoid timeouts is to write smaller queries. If you have a query which touches a lot of data – split it into several smaller queries and execute them separately.

Yeah most of the time it’s indeed because the query is too huge (for some users).

However the query linked above should work, it’s only fetching one issue with one reaction but it timeout (for some reason it seems to happens when one try to fetch user login of said reaction)