Project

Profile

Help

Bug #67

closed

Error when losing connection

Added by Vincent Le Goff over 5 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
High
Category:
Networking
Sprint/Milestone:
% 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

  1. Connect to a world.
  2. Shut down the connection (disable the WiFi, for instance).
  3. Type a command in the MUD client.
    If necessary.
  4. Reset your connection (enable the WiFi, in this example).
  5. Type another command in the MUD client.
Actions #1

Updated by Vincent Le Goff over 5 years ago

  • Description updated (diff)
Actions #2

Updated by Vincent Le Goff over 5 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
Actions #3

Updated by Vincent Le Goff over 5 years ago

  • Sprint/Milestone set to 10

Added by Vincent Le Goff over 5 years ago

Revision c377606f (diff)

Mainly fix #67: when a message can't be sent, attempt to reconnect to the server

Actions #4

Updated by Vincent Le Goff over 5 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

Also available in: Atom PDF Tracking page