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
We recently had an issue where shutting down the Fleck server (with Dispose()) did not succeed. In fact the socket restarted itself. It turned out to be caused by this code:
since RestartAfterListenError was true, when one of the open connection triggered an exception the server was automatically restarted. So for now we'll set RestartAfterListenError to false when shutting down.
The text was updated successfully, but these errors were encountered:
We recently had an issue where shutting down the Fleck server (with Dispose()) did not succeed. In fact the socket restarted itself. It turned out to be caused by this code:
since RestartAfterListenError was true, when one of the open connection triggered an exception the server was automatically restarted. So for now we'll set RestartAfterListenError to false when shutting down.
The text was updated successfully, but these errors were encountered: