-
Notifications
You must be signed in to change notification settings - Fork 252
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: handle community shard unassignment and update #4627
Conversation
Jenkins BuildsClick to see older builds (10)
|
49e1038
to
9d36709
Compare
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.
Reviewed only parts that are invoking Waku API.
Also, wondering if it is a good idea to just allow a community to switch a shard without some sort of migration warning. But this should be done at UI level i guess.
Also, it may be better to indicate the impact of doing this, as message history would be lost and any other such impact of changing shard.
9d36709
to
d3265e5
Compare
Should fix the issue described in status-im/status-desktop#13267