Netty's event loop threads are spawned lazily, i.e. they are created on the first task is scheduled on. A user sometimes wants to ensure the event loop threads are started when the server starts up.

Is your feature request related to a problem? Please describe.

As observed during #261, users can accidentally set timeouts inconsistently. A concrete example is that one can set a User facing timeout lower than any backend timeout, such that requests may fail early.

Describe the solution you'd like

We should provide some sanity checking to prevent unintended timeout behavior.

I'd love to use mercurius instead of apollo-server-lambda, so if someone has done this, please contribute even a short guide.

Is there a plan to build kernelspec with pytorch support? If not, what's the right way to contribute?
The contribution instruction page seems to be not available: https://jupyter.readthedocs.io/en/latest/contributor/content-contributor.html