{:error, :ealready}

[hermanius]

Hi,

I'm regularly (multiple times per day) getting an {error, ealready} error in efirebirdsql_op.get_response/1.
It crashes the process, and I get an error report in Sentry because of it.

The error is not handled as shown in:
get_response(Conn) ->
{ok, <OpCode:32>} = efirebirdsql_socket:recv(Conn, 4)

Is it possible to handle these kind of errors, and not let the process crash?
It would keep my Sentry logs a lot cleaner :-)

[nakagami]

tcp_gen:recv() returns {error, ealready} because tcp_gen:recv() is called by multiple processes.

• https://www.erlang.org/doc/man/gen_tcp.html#recv-3
• https://stackoverflow.com/questions/34076562/interrupting-gen-tcprecv-in-erlang

I don't know what to do either, but if there is a way to improve it, someone please let me know ?