status-im / status-desktop

Status Desktop client made in Nim & QML
https://status.app
Mozilla Public License 2.0
299 stars 79 forks source link

Communities: can't unassign community from a shard #13267

Closed anastasiyaig closed 9 months ago

anastasiyaig commented 9 months ago

Description

  1. i created a dummy QA community in 0.15 release
  2. i assigned it to non-existing shard 123
  3. i removed it from a shard (All done with UI)
Screenshot 2024-01-23 at 12 57 09
  1. i kept community untouched over the weekend (status app closed)
  2. i reopened the app and checked the community

as result, the shard is still shown as assigned to a community.

DEBUG[01-23|10:16:28.717|github.com/waku-org/go-waku/waku/v2/peermanager/peer_manager.go:222]                        subscribed topic is unhealthy, initiating more connections to maintain health pubSubTopic=/waku/2/rs/16/123 connectedPeerCount=0 optimumPeers=6
DEBUG[01-23|10:16:28.717|github.com/waku-org/go-waku/waku/v2/peermanager/peer_manager.go:228]                        could not find any peers in peerstore to connect to, discovering more pubSubTopic=/waku/2/rs/16/123
DEBUG[01-23|10:16:28.717|github.com/waku-org/go-waku/waku/v2/peermanager/peer_discovery.go:29]                       discovered peers on demand               noOfPeers=0

I need some help to clarify if we store the shard value somewhere (waku?) and shall we do that?

anastasiyaig commented 9 months ago

@richard-ramos @chaitanyaprem do you know guys if we store shard value somewhere per community?

anastasiyaig commented 9 months ago

@cammellos @osmaczko per Prem, there might be a bug in the code somewhere to store the over-ridden shard info for the community, can we please check on that?