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

spore should display peers with their advertised port, not their actual connected port. #4

Open
XertroV opened this issue Apr 21, 2014 · 1 comment

Comments

@XertroV
Copy link
Member

XertroV commented Apr 21, 2014

Sample print(spore.peers):

{('127.0.0.1', 49624): <spore.Peer object at 0x7fac484044a8>, ('127.0.0.1', 49637): <spore.Peer object at 0x7fac484368d0>, ('127.0.0.1', 32555): <spore.Peer object at 0x7fac4841f1d0>, ('127.0.0.1', 32554): <spore.Peer object at 0x7fac4aca5320>, ('127.0.0.1', 32557): <spore.Peer object at 0x7fac48422470>, ('127.0.0.1', 49628): <spore.Peer object at 0x7fac484197b8>, ('127.0.0.1', 49634): <spore.Peer object at 0x7fac4840ff98>}

Those peers with addresses not around 32555-32559 are listening on one of those ports, but it isn't displayed. There are 5 nodes total in the above network.

@ktofu
Copy link
Member

ktofu commented Jun 19, 2014

I've removed spore.peers to keep the interface as minimal as possible at the moment.

Adding useful + threadsafe functions for inspecting e.g. connected peers on the TODO list.

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

No branches or pull requests

2 participants