-
Notifications
You must be signed in to change notification settings - Fork 54
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
bug: nwaku node fails to start without a shard flag #2644
Labels
bug
Something isn't working
Comments
Agree, this should works and doesnt:
I would say shard should not default to 0. Right now it defaults to all shards. Meaning this defaults to shard 0, 1, 2, 3.
|
This looks like it has been caused by my recent fix #2633 as the error is pointing to the code that was introduced. Will take a look. |
chaitanyaprem
added a commit
that referenced
this issue
May 3, 2024
chaitanyaprem
added a commit
that referenced
this issue
May 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
Seems that shard flag was made mandatory. But I maybe it should default to 0 (like cluster id) if not passed.
And even if it's left mandatory maybe a clearer error message can be added so the node operator is aware that shard is mandatory
nwaku version/commit hash
harbor.status.im/wakuorg/nwaku:latest
The text was updated successfully, but these errors were encountered: