fix: start watchTopicShards once #1298
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
igor-sirotin
force-pushed
the
fix/duplicated-call-watch-rs
branch
from
37f322e to
4be813d
Compare
igor-sirotin
requested review from
chaitanyaprem and
richard-ramos
as code owners
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
watchTopicShardsis now guarded with a flag. I've found that it was called more than once.Note that
setupENRis called once at startup, and then each time multiaddrs change. That makes it least twice.logos-messaging-go/waku/v2/node/wakunode2.go
Line 350 in 04176c0
logos-messaging-go/waku/v2/node/wakunode2.go
Line 476 in 04176c0