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

peer unresponsive #120

Open
wfleurant opened this issue Jan 30, 2018 · 7 comments
Open

peer unresponsive #120

wfleurant opened this issue Jan 30, 2018 · 7 comments

Comments

@wfleurant
Copy link
Member

it would be neat if the repo were able to serve up a magic online/offline image -- table of peers with status image?

@lvlts
Copy link

lvlts commented Feb 12, 2018

Hi @wfleurant

I've made a daily Travis CI build scenario. It compiles cjdns, pulls a copy of hyperboria-peers from npm and builds a config file containing all peers. Then compiles a table showing responsive and non-responsive peers, after an interval of 180 seconds.

The result is here: https://lvlts.github.io/hyperboria-peer-check/
The repository doing the checks is here: https://github.com/lvlts/hyperboria-peer-check

This only works for IPv4 peers. Sorry, I didn't have time to work out all scenarios. Documentation is lacking, I'll probably look over it over the following weeks, if I get any spare time.

@ansuz
Copy link
Member

ansuz commented Feb 12, 2018

That's fantastic!

@wfleurant
Copy link
Member Author

should readme link to hype-peer-check?

@kpcyrd
Copy link
Member

kpcyrd commented Feb 26, 2018

If @lvlts is ok with this, I would include the travis script in this repo with some changes:

  • If it's a PR, only verify the new node(s) is working, fail the build if it doesn't work
  • If it's a periodic build, verify all nodes, fail the build unless everything works
  • Include the travis badge in the readme

This can detected with $TRAVIS_EVENT_TYPE as described here: https://docs.travis-ci.com/user/environment-variables/#Default-Environment-Variables

@lvlts
Copy link

lvlts commented Mar 1, 2018

@kpcyrd hi, I have no issue with the code being reused in any way you see fit. Please keep in mind that licensing is currently restricted to GPLv3 due to this, which is a modified version of the one used in cjdns. I have no problems with changing the licensing if the dependency is replaced by anything else.

I am currently a little bit pressed on time, so if you are willing to implement the above changes by yourself, it would be great. I can spare some times in a few weeks, at least.

Thanks!

@wfleurant
Copy link
Member Author

Do we need a travis builder? Does lvlts/hype-check need to make it's way to this hype/peers or is hype/peers linking to the travis badge?

Shoot.

@whoizit
Copy link

whoizit commented May 24, 2018

we have this from russian community http://cjdns.cupivan.ru/

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

No branches or pull requests

5 participants