adobe / adobe/node-fetch-retry
Error cannot be intercepted request-timeout, body-timeout, etimedout, econnreset
Open
- Dominant language
- JavaScript
- Stars
- 44
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
-
Contributor guide
Research direction
Start by reproducing the request-timeout, body-timeout, ETIMEDOUT, and ECONNRESET cases described in the title, then trace how node-fetch-retry propagates those errors. Done means the relevant timeout and connection-reset errors can be intercepted reliably; the issue provides no file or test entry point, so locating the handling code is part of the work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100