all ngql statements running throw error after a socket timeout

[huaxiabuluo]

Describe the bug (must be provided)

when we set GraphServiceTimeout a value of 5s, it will throw errors after a socket request timeout.

errors like:

• read tcp 10.8.0.34:64072->192.168.8.131:9669: i/o timeout
• ErrInternalServer::execute failed: out of sequence response
• ErrInternalServer::Invalid data length
• ...

so we make GraphServiceTimeout a value of long timeout

// set the timeout for the graph service: 8 hours
// once the timeout is reached, the connection will be closed
// all requests running ngql will be failed, so keepping a long timeout is necessary, make the connection alive
const GraphServiceTimeout = 8 * time.Hour

Your Environments (must be provided)

• OS: Linux,Mac or Windows
• Node-version: node --version
• Studio-version: display in studio navBar

How To Reproduce(must be provided)

Steps to reproduce the behavior:

1. Step 1
2. Step 2
3. Step 3

Expected behavior

A clear and concise description of what you expected to happen.

Additional context

Provide logs and configs, or any other context to trace the problem.