-
Notifications
You must be signed in to change notification settings - Fork 42
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
autosharding content-topic config #696
Conversation
…until redesign of store is done
Jenkins BuildsClick to see older builds (48)
|
@richard-ramos , in nwaku if topic validation fails the node doesn't start with an error indicating named and static shards to be not used simultaneously. But in go-waku case we seem to be proceeding ahead and just logging a warning. |
Oops! this was an oversight when I implemented that functionality. #699 fixes this, since we do need static and named shards for now in status-go |
PR looks good to me. |
Ah...missed compiling and updating examples. Will do that as well in this PR only. |
Description
New config to specify pubsub and contentTopics.
ENR updation as per config.
Changes
Tests
enr:-Jq4QAks1JpiJ8kjKXZbUvNEjDJb5F7u1xtIyb9XXZtVEhIvHhVpDb53CQpeknyWEr5dw0U-gVFqdm-4V-blSMvAomyGAYpKuzUMgmlkgnY0gmlwhMCoAQyCcnOFAAEBAAOJc2VjcDI1NmsxoQINUHz8nP1tgbfQv4-_Aqw-enrekJpmX6u0ASpuEUPnnoN0Y3CC6mCFd2FrdTIB