Undici BalancedPool routes to an unreachable upstream server and does not handle it gracefully, causing an UND_ERR_CONNECT_TIMEOUT
Open
Nobody has claimed this yet.
bug
- Dominant language
- JavaScript
- Stars
- 7.7k
- Forks
- 880
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 68
Description
See the comment on the referenced issue
https://github.com/mercurius-js/mercurius-gateway/issues/64#issuecomment-1438038031
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the referenced Mercurius Gateway issue comment, then trace Undici's BalancedPool behavior when an upstream server is unreachable and produces UND_ERR_CONNECT_TIMEOUT. Define graceful handling for that failure and verify it with focused coverage for an unreachable upstream.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100