Konrad Komorowski

I guess there is theoretically the 4th option of the lifecycle hooks waiting for also the unneeded resolvers to finish. I wonder though if the HTTP response concluding before the...

Oh, I think there is a decent variation on option 4! What if it was possible to configure a schema extension to wait for **all** resolvers to finish before concluding?...

> Is there any particular reason why you're doing this on an extension and not using your web framework functionality? That's a very good question! The context we prepare is...

Ok, reported this to `graphql-core`: https://github.com/graphql-python/graphql-core/issues/217 - thanks for the suggestion @nrbnlulu ! @patrick91 – I'll play with using FastAPI for it, but I've realised that there may be a...

A little update from graphql-core - it was acknowledged as something the maintainer did want to address as well. :) https://github.com/graphql-python/graphql-core/issues/217#issuecomment-2015919484 So the issue is definitely real - but not...

Just to add my 0.02 USD here – I'm not a maintainer, but I'm following this project. I would side with @RobertCraigie's view here – I think there should be...

I would like to +1 this! For us, this happens maybe once a day just during continuous deployment (so not counting PRs). The errors we're seeing look like transient infrastructure...

Came across this PR when looking at #9951 – thank you for adding this rule, very excited about it! Regarding the latest discussion – I'm curious why not omit it...

Thanks so much for the quick response @Cito! Are there *any* thoughts / pointers you can share yourself? Don't want to make any promises, but I might be able to...

Specifically I would appreciate it if you could point me to the parts of the code which do the collection of results and skipping of execution when an incoercible error...