You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i kept community untouched over the weekend (status app closed)
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?
The text was updated successfully, but these errors were encountered:
@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?
Description
as result, the shard is still shown as assigned to a community.
I need some help to clarify if we store the shard value somewhere (waku?) and shall we do that?
The text was updated successfully, but these errors were encountered: