Sameer Srivastava

Added a new test case and updated some existing ones. Please review

> The inner error message is already being set as the `message` property on the error in the existing implementation. I am not sure if we have any more information...

@jonnydgreen I have updated the docs. Can you please take a look? Thanks

Maybe you could try using the `errorFormatter` callback to clean up the container instance. Something like: ```js app.register(mercurius, { schema, resolvers, context: ({ request, reply }) => { return {...

As per my understanding, I think `didEncounterErrors` hook captures errors occurred while parsing or validating a GraphQL operation. In mercurius, those errors can be captured in the `errorFormatter` instead of...

@j I guess these http errors can be handled using a custom `errorFormatter` (https://mercurius.dev/#/docs/api/options?id=error-formatter). Have you tried it?

@mcollina Do you think we should we should change the error implementation in mercurius to accommodate these http errors or leave it for now since the same can be achieved...

@mcollina Do you mean we should remove the `errors` property if the error is thrown by a fastify-plugin before the request reaches GraphQL?

@j can you please provide the code snippet that reproduces the issue? especially the part that triggers this particular error.

Facing the same issue after installing the latest version from the releases page. I don't have any antivirus or firewall on my system. Is there any fix for this yet?...