aws / aws/firelens-datajet

Connect failures should mention the port number

Open
#24 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
EJS
Stars
7
Forks
14
PR merge metrics
No merged PRs in 30d

Description

I got this error:

```
node:events:491
throw er; // Unhandled 'error' event
^

Error: read ECONNRESET
at TCP.onStreamRead (node:internal/stream_base_commons:217:20)
Emitted 'error' event on Socket instance at:
at emitErrorNT (node:internal/streams/destroy:157:8)
at emitErrorCloseNT (node:internal/streams/destroy:122:3)
at processTicksAndRejections (node:internal/process/task_queues:83:21) {
errno: -104,
code: 'ECONNRESET',
syscall: 'read'
}
```

I have multiple TCP data jets running, so its not clear from the error which one of them failed. Or if its a TCP datajet of a forward datajet.

Contributor guide

Open the contributing guide

Research direction

No file or test is named. Start by tracing TCP datajet connection setup and error handling, including forward datajets; done means connection failures identify the affected port so multiple running datajets can be distinguished.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js
Domain
backend, networking
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.