Actions
Bug #67
closedError when losing connection
% Done:
100%
Company:
-
Contact person:
-
Additional contact persons:
-
Description
At times, CocoMUC fails to notice that the connection is broken. When entering a command, however, the following traceback appears:
Traceback (most recent call last): File "C:\Users\Vincent\src\cocomud\src\log.py", line 224, in run_with_except_hook run_original(*args2, **kwargs2) File "C:\Users\Vincent\src\cocomud\src\client.py", line 89, in run msg = self.client.read_very_eager() File "C:\python27\lib\telnetlib.py", line 416, in read_very_eager self.fill_rawq() File "C:\python27\lib\telnetlib.py", line 576, in fill_rawq buf = self.sock.recv(50) error: [Errno 10054] An existing connection was forcibly closed by the remote host
Steps to reproduce¶
- Connect to a world.
- Shut down the connection (disable the WiFi, for instance).
- Type a command in the MUD client.
If necessary. - Reset your connection (enable the WiFi, in this example).
- Type another command in the MUD client.
Updated by Vincent Le Goff almost 8 years ago
A similar error occurs sometimes:
Traceback (most recent call last): File "C:\Users\Vincent\src\cocomud\src\log.py", line 224, in run_with_except_hook run_original(*args2, **kwargs2) File "C:\Users\Vincent\src\cocomud\src\client.py", line 89, in run encoding = self.engine.settings["options.general.encoding"] File "C:\python27\lib\telnetlib.py", line 416, in read_very_eager self.fill_rawq() File "C:\python27\lib\telnetlib.py", line 576, in fill_rawq buf = self.sock.recv(50) error: [Errno 10054] An existing connection was forcibly closed by the remote host
Added by Vincent Le Goff almost 8 years ago
Updated by Vincent Le Goff almost 8 years ago
- Status changed from Open to Closed
- Assignee set to Vincent Le Goff
- % Done changed from 0 to 100
Mostly fixed in commit c377606f5def2a6ddd14ab97132cb1003b3aeed5.
The client now attempts to reconnect if a connection error occurs. However, this doesn't eliminate connection issues altogether.
Please register to edit this issue
Actions
Also available in: Atom PDF Tracking page
Mainly fix #67: when a message can't be sent, attempt to reconnect to the server