Skip to content

The module causes unhandledRejection #374

@wzrdtales

Description

@wzrdtales

We just stumbled upon this and found out this module was responsible for it.

When there are errors such as connection errors, this module will not properly catch the errors and pass them through.

This makes working code to malfunction as soon as the transportagent is installed, whenever there are network level issues such as ETIMEDOUT.

[ERROR] unhandledRejection
[ERROR] AggregateError [ETIMEDOUT]: 
    at internalConnectMultiple (node:net:1139:18)
    at internalConnectMultiple (node:net:1215:5)
    at Timeout.internalConnectMultipleTimeout (node:net:1741:5)
    at listOnTimeout (node:internal/timers:590:11)
    at process.processTimers (node:internal/timers:523:7)

This most likely stems from here:

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions