-
Notifications
You must be signed in to change notification settings - Fork 57
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
chore: update content-topic parsing for filter #2835
Conversation
You can find the image built from this PR at
Built from 350796b |
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.
Great catch, thank you!
I think this should be run only if relay is configured. If filter is configured and relay isn't, with these changes we would still mount relay nwaku/waku/factory/node_factory.nim Lines 160 to 168 in 9691dfb
|
Thanks for suggesting @gabrielmer ! |
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.
Thanks so much!
Added a last detail to align :))
waku/factory/node_factory.nim
Outdated
if conf.relay: | ||
let shards = | ||
conf.contentTopics.mapIt(node.wakuSharding.getShard(it).expect("Valid Shard")) | ||
let pubsubTopics = conf.pubsubTopics & shards | ||
|
||
debug "Shards created from content topics", |
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.
I think we should move this log to be right below
nwaku/waku/factory/node_factory.nim
Lines 147 to 148 in 11b575d
let shards = | |
conf.contentTopics.mapIt(node.wakuSharding.getShard(it).expect("Valid Shard")) |
close #2834
This is a minor change to fix bug #2834.