Problem
The routeParser.ts crawls and probes target application links during route discovery. If a target URL contains broken links, dead ports, or hangs indefinitely, the pipeline run gets stuck without terminating properly.
Proposed Solution
Add an explicit timeout configuration (e.g., 5000ms maximum per request hook) via the native fetch options inside the httpClient or the parser directly to cleanly reject hung sockets.
File(s) to Modify
lib/attack-pipeline/parsers/routeParser.tslib/attack-pipeline/utils/httpClient.ts
I want to work on this issue. Please assign it to me.
Problem
The
routeParser.tscrawls and probes target application links during route discovery. If a target URL contains broken links, dead ports, or hangs indefinitely, the pipeline run gets stuck without terminating properly.Proposed Solution
Add an explicit timeout configuration (e.g., 5000ms maximum per request hook) via the native fetch options inside the
httpClientor the parser directly to cleanly reject hung sockets.File(s) to Modify
lib/attack-pipeline/parsers/routeParser.tslib/attack-pipeline/utils/httpClient.tsI want to work on this issue. Please assign it to me.