Open dovydas55 opened 4 years ago
This is probably way too late to be useful to you, but I was seeing a similar issue. It boiled down to the sender (client) expecting the recipient to close the connection by default which it wasn't doing.
Adding the "ImmediatelyCloseReqBody" flag to the client instantiation fixed the issue of stale connections lying around:
client := graphql.NewClient("https://example.com/graphql", graphql.ImmediatelyCloseReqBody())
This is probably way too late to be useful to you, but I was seeing a similar issue. It boiled down to the sender (client) expecting the recipient to close the connection by default which it wasn't doing.
Adding the "ImmediatelyCloseReqBody" flag to the client instantiation fixed the issue of stale connections lying around:
client := graphql.NewClient("https://example.com/graphql", graphql.ImmediatelyCloseReqBody())
apparently it is still useful! encountering EOF but couldn't scratch my head on the reason. Will try this out! thank you.
Edit: tried the solution, doesn't work still encountering the same issue, for us it's the router we are using that causes the issue
Has anyone seen this kind of error before? I ran this client on a loop for the last 12 hours, and around once every hour i noticed this error. It did not return any other contextual information