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
At lantern listener side (http-proxy), when we make a multiplex listener/wrap listeners, we return a custom connection type (idleConn - there's other custom connections/listeners under the same package, most of them are implementing net.Conn). As an WATER user I want to be able send a custom net.Conn and use this connection to successfully communicate.
Currently when I try to provide an idle connection I got the following error message:
At lantern listener side (http-proxy), when we make a multiplex listener/wrap listeners, we return a custom connection type (idleConn - there's other custom connections/listeners under the same package, most of them are implementing
net.Conn
). As an WATER user I want to be able send a customnet.Conn
and use this connection to successfully communicate.Currently when I try to provide an idle connection I got the following error message:
This message is being triggered here, falling into the default condition, since the custom connection is not supported.
The text was updated successfully, but these errors were encountered: