-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
fix two pubsub issues. #7394
fix two pubsub issues. #7394
Conversation
Stebalien
commented
May 29, 2020
- Flood for first pubsub hop to ensure the message gets broadcasted even if some of our peers are overloaded.
- Remove discovery logic. This is now handled by pubsub internally.
When publishing a value, flood. This ensures that our messages make it to the network even if some of our peers are bad and/or overloaded.
Pubsub handles this internally now.
@achingbrain this now floods on initial publish. However, looking at the failure, publishing from go isn't the issue so flooding from go doesn't help. |
I'm also not sure what is wrong with the ipns interop tests. |
I've been trying to isolate the problem and I'm not getting very far. It's definitely the go/js interactions - go/go and js/js seem to pass. The failures are intermittent, though appear on Linux the most frequently. I've been running it with js-libp2p-gossipsub logging turned on, and the weird thing is from the JS end the log lines are identical between passing and failing test runs (if you ignore the peer IDs and transferred data): Passing:
Failing:
A weird thing is that Go sends two RPC messages to JS but only in the first test. Then again it does it in both the successful and the failed runs. Maybe @vasco-santos @jacobheun or @wemeetagain know more about what's going on in the gossipsub module internally? How can I get more logging out of the go-ipfs daemon? |
@achingbrain you can run |
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 (modulo failing interop tests)
Merging as the interop tests are already broken. I've added a line to the 0.6.0 todo list to fix this issue. |