Internal error occurred during message handling / EIPE

[theogravity]

graphql-ws sometimes prints out the following message:

https://github.com/enisdenjo/graphql-ws/blob/master/src/use/ws.ts#L140

Internal error occurred during message handling. Please check your implementation. Error: write EPIPE

Based on reading about write EPIPE errors, it seems that the client has disconnected during this phase:

https://github.com/enisdenjo/graphql-ws/blob/master/src/server.ts#L590

In our logging infra, it goes across many lines and looks like this:

• Should we be able to define the logger we want to use for errors so we can parse them to how we want?
• What's the best way to catch this kind of error when it happens and where should it be done?
• Is it something on our side or really due to the client disconnecting during processing?

I wonder if my issue is the same as #333

We do have a lot of complex logic that could potentially throw in our subscription handlers...

[enisdenjo]

Should we be able to define the logger we want to use for errors so we can parse them to how we want?

I'd recommend implementing your own server instead. You can then handle the errors however you see fit. For a quick start, please consult the "Server usage with ws" recipe.

What's the best way to catch this kind of error when it happens and where should it be done?

All possible errors that could be thrown during operation execution can be handled using the onMessage callback argument. Read more about it in the documentation.

Is it something on our side or really due to the client disconnecting during processing?

I've never faced this error myself, so I cannot shine more light on this question. If it is indeed #333, my recommendation is to just handle the errors properly in the subscribe handlers.