This repository has been archived by the owner on Oct 10, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 87
Unhandled socket hung up
introduced with http-proxy
#264
Comments
Yep I had seen this also, see https://github.com/defunctzombie/zuul/pull/256/files. I thought I fixed it but maybe not. |
bouncy had attached a listener destroying the socket when error occurred by default. That behavior I didn't found in http-proxy module. Not sure either it's the desired behavior but at least there should be an error handler registered. |
Do you know where we should register it, or if it's an http-proxy task? Maybe there's an issue in their github |
Ok, do you think you can provide a PR to zuul to handle this? |
Hey, just saw this issue. I fixed the same issue here (webtorrent/webtorrent.io@cd4cb63) recently. Hope this helps! |
focusaurus
added a commit
to focusaurus/peterlyons.com
that referenced
this issue
Mar 21, 2016
Downgrade zuul to avoid defunctzombie/zuul#264
focusaurus
added a commit
to focusaurus/peterlyons.com
that referenced
this issue
Mar 21, 2016
Downgrade zuul to avoid defunctzombie/zuul#264
Closed
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I keep getting this error code when running with
[email protected]
and[email protected]
.This doesn't happen with
[email protected]
, before the introduction ofhttp-proxy
. If you follow the line of the thrown error:The text was updated successfully, but these errors were encountered: