This repository has been archived by the owner on Jan 15, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 44
Who is eating our connections? #1492
Comments
4 tasks
We need to destroy free sockets explicitly. Related to request/forever-agent#30. |
We've fixed forever agent and now our test can be stopped only because of |
We've created our fork of forever-agent, see thaliproject/forever-agent. |
@larryonoff I thought @andrew-aladev said we still have a slow leak and should keep this issue open but at a lower priority since the leak looks quite slow? |
@yarong we still have leak, but very slow. It least as we know now. So I'm reopening the issue but lower the priority. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Someone is sitting on our connections and making us run out. Who is it?
The text was updated successfully, but these errors were encountered: