Carlos Fuentes
Carlos Fuentes
I'm leaning more into the side of fix it; if we want to play friendly, we can add a check to handle that situation just if `application/json` and the body...
Can you provide an [Minimum Reproducible Example](https://stackoverflow.com/help/minimal-reproducible-example) to support you better?
Hmm, this does not seem like an `undici` error per se but rather a different way of handling connect timeouts. The errors shown by the example and the roots of...
The timeouts you mention are applied directly at `http` level, meanwhile the `timeout` I'm referring to, is linked to the TCP handshake; which by default is `10s` (lower than the...
Is still reproducible or it can be closed after #3707 landed?
I'd rather say that is not really an `undici` nor `node.js` problem as it can be sorted out by extending the timeout for the DNS resolution; might be worth it...
Do you have the PR at hand? Why was removed? If seeking to extend the timeout, I'd suggest opening an issue in Node.js with the reference to the other issues...
can you just address the recommendation there?
Yes, exactly; sorry for the confusion, was referring to the wrapper
The concatenation is something that only seems to happen on `fetch`, attempting the same with `undici#request` does lead to the expected result of an array instead of a concatenated string....