Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disconnect from peer can kill spore (so reconnect is impossible) #14

Open
XertroV opened this issue Aug 24, 2014 · 1 comment
Open

Disconnect from peer can kill spore (so reconnect is impossible) #14

XertroV opened this issue Aug 24, 2014 · 1 comment
Assignees
Labels
Milestone

Comments

@XertroV
Copy link
Member

XertroV commented Aug 24, 2014

Future/Task exception was never retrieved
future: Task(<_connect_loop>)<exception=TimeoutError(110, "Connect call failed ('220.233.5.76', 2281)")>
Traceback (most recent call last):
  File "/usr/lib/python3.4/asyncio/tasks.py", line 298, in _step
    result = coro.throw(exc)
  File "/usr/local/lib/python3.4/dist-packages/spore-0.9.4-py3.4.egg/spore/__init__.py", line 239, in _connect_loop
    local_addr=local_addr)
  File "/usr/lib/python3.4/asyncio/base_events.py", line 419, in create_connection
    raise exceptions[0]
  File "/usr/lib/python3.4/asyncio/base_events.py", line 410, in create_connection
    yield from self.sock_connect(sock, address)
  File "/usr/lib/python3.4/asyncio/futures.py", line 348, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/lib/python3.4/asyncio/tasks.py", line 351, in _wakeup
    value = future.result()
  File "/usr/lib/python3.4/asyncio/futures.py", line 243, in result
    raise self._exception
  File "/usr/lib/python3.4/asyncio/selector_events.py", line 300, in _sock_connect
    raise OSError(err, 'Connect call failed %s' % (address,))
TimeoutError: [Errno 110] Connect call failed ('220.233.5.76', 2281)
@XertroV XertroV added this to the 0.9.5 milestone Aug 24, 2014
@XertroV XertroV added the bug label Aug 24, 2014
@XertroV XertroV self-assigned this Aug 24, 2014
@XertroV
Copy link
Member Author

XertroV commented Aug 24, 2014

Hmm, this will always fail (in this case) because 220.233.5.76 was me and the client was behind a NAT. This is going to come up a lot, then, so should be dealt with in an appropriate manner.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant