Error: socket hang up

[ala85]

What happened?

Sometimes, when not interacting with the chat after a few successful prompts with Bedrock, I get the error:

AI response error; aborting request: TypeError: Cannot read properties of undefined (reading 'status')

This is not though the real cause (a null pointer exception), but rather a consequence of Axios not being able to handle the connection.
The underlining reason of this bug is due to Error: socket hang up

 cause: Error: socket hang up
      at TLSSocket.socketOnEnd (node:_http_client:535:25)
      at TLSSocket.emit (node:events:531:35)
      at endReadableNT (node:internal/streams/readable:1696:12)
      at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
    code: 'ECONNRESET'

The /query endpoint seems the one causing it.
I tried to setup explicitly the httpAgent and httpsAgent as below:

const httpsAgent = new https.Agent({ keepAlive: true });

...
return axios.post(
      `${process.env.RAG_API_URL}/query`,
      {
        file_id: file.file_id,
        query: userMessageContent,
        k: 4,
      },
      {
        headers: {
          Authorization: `Bearer ${jwtToken}`,
          'Content-Type': 'application/json',
        },
        httpsAgent,
        httpAgent: httpsAgent
      },

but didnt help much.

Is this a common issue?

Steps to Reproduce

1. Interact with Bedrock chat for a while
2. Make sure prompts and response are successful.
3. After being idle for a minute or so retry

What browsers are you seeing the problem on?

Chrome

Relevant log output

cause: Error: socket hang up
      at TLSSocket.socketOnEnd (node:_http_client:535:25)
      at TLSSocket.emit (node:events:531:35)
      at endReadableNT (node:internal/streams/readable:1696:12)
      at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
    code: 'ECONNRESET'
  }
}
2024-10-07T12:44:23.626Z error: Error creating context: Cannot read properties of undefined (reading 'status')
2024-10-07T12:44:23.627Z error: [handleAbortError] AI response error; aborting request: Cannot read properties of undefined (reading 'status')
[handleAbortError] AI response error; aborting request: TypeError: Cannot read properties of undefined (reading 'status')
    at /app/packages/data-provider/dist/index.js:1:163557
    at /app/packages/data-provider/dist/index.js:1:2003
    at Object.next (/app/packages/data-provider/dist/index.js:1:2108)
    at /app/packages/data-provider/dist/index.js:1:951
    at new Promise (<anonymous>)
    at v (/app/packages/data-provider/dist/index.js:1:696)
    at /app/packages/data-provider/dist/index.js:1:163390
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Axios.request (/app/node_modules/axios/dist/node/axios.cjs:4257:14)
    at async Promise.all (index 0)
    at Axios.request (/app/node_modules/axios/dist/node/axios.cjs:4262:41)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Promise.all (index 0)
    at async Object.createContext (/app/api/app/clients/prompts/createContextHandlers.js:101:31)
    at async Promise.all (index 0)
    at async Object.createContext (/app/api/app/clients/prompts/createContextHandlers.js:101:31)
    at async AgentClient.buildMessages (/app/api/server/controllers/agents/client.js:282:30)
    at async AgentClient.sendMessage (/app/api/app/clients/BaseClient.js:535:9)
    at async AgentController (/app/api/server/controllers/agents/request.js:90:20)
    at async /app/api/server/routes/bedrock/chat.js:32:5
2024-10-07T12:44:23.642Z debug: [AgentController] Request closed

Screenshots

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[danny-avila]

There is no way to reproduce this from the report. Are you able to use file attachment features at all?

[ala85]

Yes I can by using the rag api repo. The error seems to happen randomly as axios fails the api call. I ll try to provide further logs and steps to reproduce.

[ala85]

After a few tries, it is definetely related with file attachment.

It happens most of time when you start a conversation by asking a question with an attached file. Only way to "fix" it is to refresh page. Sometimes it helps also asking a question to LLM without any file attached such as "Hi", and then seems to re-work.

I am using last version with no code customizations.