-
Notifications
You must be signed in to change notification settings - Fork 961
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
#1436 triggers assertion failure in libp2p-kad
#1437
Comments
Is there an easy way to reproduce this, i.e. does it occur pretty much every time #1436 is used with substrate in debug mode? |
Yes, it did happen to me every single time with #1436 after some minutes. |
I managed to reproduce it three times. The cause seems to be outside of The summary is that
because the Kademlia keyspace is essentially based upon Troubleshooting this can be quite confusing because peer IDs that appear visually different as per their I don't know yet how best to resolve this, but thought it makes sense to already share my findings here. |
So this is most definitely unrelated to #1436 and thus needn't block these changes, as I initially feared. |
I guess #1444 will temporarily address this issue as well, though not long-term. As far as I can currently tell, |
We could simply use the SHA256 hash all the time for comparison. |
Testing #1436 with substrate causes an assertion failure in
libp2p-kad
(when compiled in debug mode):The text was updated successfully, but these errors were encountered: