We noticed last night that there is a race condition in FtlClient that can lead to a double close of a socket, for now protecting with a mutex following an identical pattern to what NetworkSocketConnectionTransport does.
Verified locally by refreshing a single viewer several times to stop/create new edge ftl clients.
We noticed last night that there is a race condition in FtlClient that can lead to a double close of a socket, for now protecting with a mutex following an identical pattern to what NetworkSocketConnectionTransport does.
Verified locally by refreshing a single viewer several times to stop/create new edge ftl clients.
Might help with #115