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
This is one for me. Testing by connecting to Fuzzball without ssl on the ssl port and typing garbage will close the socket on the user's side. Presently mutgos does not. This issue is to fix this to be sure my code is not leaking sockets.
The text was updated successfully, but these errors were encountered:
That is a little tricky with boost, since they use smart pointers and such. You'll likely need to use valgrind to confirm it's working as expected. Sometimes I've seen the last socket hang around even after disconnect... so you may need to connect multiple times and confirm it's releasing them. I don't expect it to be too hard to fix, though, and is likely just a couple of lines.
This is one for me. Testing by connecting to Fuzzball without ssl on the ssl port and typing garbage will close the socket on the user's side. Presently mutgos does not. This issue is to fix this to be sure my code is not leaking sockets.
The text was updated successfully, but these errors were encountered: