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
Hi,
I have encountered a difference between Windows and Linux.
In Linux, if I close the connection from the server, the close()-function is called, and reason and other stuff are nicely presented to the client.
In Windows, only the closed(self, code, reason=None)-function is called, and not the close()-function.
I rather get the "ConnectionResetError: [WinError 10054] An existing connection was forcibly closed by the remote host".
The above error may be because the first close doesn't happen property and it is because the server is shutting down. But if so, the same thing would happen under Linux. It is kind of hard to say, as it is multiprocessing and so forth, so the order of logs differ depending on how quickly stuff happens on each platform.
It is completely possible that I am missing something, of course, but still..
The text was updated successfully, but these errors were encountered:
So this sort of sorted itself out. Suddenly it sort of happened less and less, I am suspecting that this was since the performance(process initialization) was worse under windows.
Closing.
Hi,
I have encountered a difference between Windows and Linux.
In Linux, if I close the connection from the server, the close()-function is called, and reason and other stuff are nicely presented to the client.
In Windows, only the closed(self, code, reason=None)-function is called, and not the close()-function.
I rather get the "ConnectionResetError: [WinError 10054] An existing connection was forcibly closed by the remote host".
The above error may be because the first close doesn't happen property and it is because the server is shutting down. But if so, the same thing would happen under Linux. It is kind of hard to say, as it is multiprocessing and so forth, so the order of logs differ depending on how quickly stuff happens on each platform.
It is completely possible that I am missing something, of course, but still..
The text was updated successfully, but these errors were encountered: