You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Without destroying the various HTTP and HTTPS agents Assetgraph can keep the event loop open for a long time just waiting for keep-alive connections to be closed. There should be a method on Assetgraph that calls the quit() method on Teepee member instance. This will close the persistent connections held open by the agents.
Thank you,
Rusty
The text was updated successfully, but these errors were encountered:
Might be even better if we can configure the http(s) agents to only use keep-alive when a new request is made within a tick of the previous one completing. Then we wouldn't need to increase the api surface.
I assume that by "a long time" you mean that you're seeing it holding on to the connections (or at least keeping the event loop alive) for longer than that? Can you share an example?
Hi Team,
Without destroying the various HTTP and HTTPS agents Assetgraph can keep the event loop open for a long time just waiting for keep-alive connections to be closed. There should be a method on Assetgraph that calls the
quit()
method on Teepee member instance. This will close the persistent connections held open by the agents.Thank you,
Rusty
The text was updated successfully, but these errors were encountered: