-
Notifications
You must be signed in to change notification settings - Fork 971
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
service/header: fix ExtendedHeader message duplicates on the network #409
Conversation
#237 seems like a PR, did you link to the right thing? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice fix! Left a comment nit.
Thank you for catching this. No, I linked the wrong thing.
|
Co-authored-by: John Adler <[email protected]>
Co-authored-by: rene <[email protected]>
5d8fff6
to
4a6cf9c
Compare
Just tested manually on my node that this works as expected and there are no duplicate header logs anymore! |
…ing validation and document error handling
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
A quick note that we are now maintaining our own fork of pubsub due to #409 (comment) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! No objections from my side. I'd give the inner msgID
function a different name though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
+1 to @liamsi comment re: issue for dep
What
Finally, a fix to solve this longstanding issue.
How
By using a new feature in libp2p/go-libp2p-pubsub#468 we can now implement custom per-topic message id generation where for the 'HeaderSub' we avoid Signatures from being hashed.
TODO
- [ ] An integration test to assert this is exactly trueWe don't have a way to fully simulate this case, as we don't have a test suite to run multiple core validating nodes per test, which we need to rcv multiple headers with different commit set.
Closes #236