-
Notifications
You must be signed in to change notification settings - Fork 568
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UND_ERR_HEADERS_TIMEOUT received even when setting a larger headersTimeout in dispatcher for fetch() #1864
Comments
How is the agent instantiated? |
I just got this sample working to reproduce the issue. Changing the delay at the top to less than 4 is fine, and greater than 5 minutes and it fails I was able to do this same test with a Client and it seems to work fine, so something specific to fetch() I think
|
versus this (just substituted fetch() and agent with a client) which runs "fine"
|
Also here is what I am testing with locally xconverge@de7f4c0 |
PR opened for this. |
Thanks! |
Bug Description
I am trying to make a fetch request that can take 5+ minutes.
I make a fetch() request with a custom Agent containing atleast these parameters (I have also overridden connect for overriding checkServerIdentity())
fetch() call looks like this:
yet after about ~200 seconds I am getting a headers timeout
Reproducible By
Performing a LONG fetch operation
Expected Behavior
I would expect some combination of me setting headerTimeout to either 0 or a very high number to not trigger this timeout.
Logs & Screenshots
Environment
Ubuntu 20 in WSL, Node 18
Additional context
I have seen some stuff related to "blocking" https://undici.nodejs.org/#/docs/api/Dispatcher but am unable to figure out where to set it and am unsure if its even related
The text was updated successfully, but these errors were encountered: