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
Since v0.7.2 where the tcp socket is set to active mode. This causes issues when someone want full control of the underlying tcp socket.
In my case I get the socket and set active to false, so once I try to :gen_tcp.recv and the socket try to send a message in another process, I get the error {:error, :einval} (because the socket is set to active mode)
The text was updated successfully, but these errors were encountered:
Hi, I see the issue. In membraneframework/membrane_rtsp#44 the behavior changes (after transferring control the session no longer tries to receive from that socket). Would it be okay if it's fixed there?
Since v0.7.2 where the tcp socket is set to active mode. This causes issues when someone want full control of the underlying tcp socket.
In my case I get the socket and set
active
to false, so once I try to:gen_tcp.recv
and the socket try to send a message in another process, I get the error{:error, :einval}
(because the socket is set to active mode)The text was updated successfully, but these errors were encountered: