-
Notifications
You must be signed in to change notification settings - Fork 4
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
Invalid peers can get stuck in member list #5
Comments
Question: Was the invalid node propagated to other's peer lists? This seems impossible because nodes don't add a peer until they get a reply from them. But there could be a race condition somewhere. |
You'll have to forgive me for how imprecise my steps for reproducing this are. As you say, it's likely a race condition, so I won't spend any more effort trying to get the timing correct. It may take a few attempts for this to work. Let me know if you're having any trouble. save this as
create a bash script in the same directory:
run this bash script and continually hit If you don't want to bother with this, let me know, and I will target your node myself. |
Can you check if this is still an issue? |
This issue still exists as of c97e6a4 . Again, if you don't feel like doing this, I can target your node. Almost certainly a race condition, so the following process might take a few attempts. https://gist.github.com/Alrighttt/fd52f202f38dbc95ccfc71427382683f Now quickly run this about 1000 times. |
This should not be a difficult one to solve, @Alrighttt has a script which connects to a zeno node and can send an invalid reply port which ends up getting stuck in the node's peer list. Reproduction pending.
The text was updated successfully, but these errors were encountered: