[Epic] Targeted dogfooding for Status Communities

[fryorcraken]

Epic label: E:Targeted Status Communities dogfooding

Summary

Dogfooding of delivery for Status Communities (static sharding, PostgreSQL, opt-in message signing).

Acceptance Criteria

• Fleet setup for Status staging Setting up static sharding fleet for Status nwaku#1914
• Basic testing go-waku in Status Desktop + nwaku PostgreSQL/Static Sharding
• Document Fleet maintenance to handover to Status docs: requirements for being a Waku fleet owner #61

Tasks

[fryorcraken]

@richard-ramos I think we can close waku-org/nwaku#1914 so let's use this epic to track the work you are doing to test static sharding with Status Desktop.

[richard-ramos]

Weekly Update

• achieved: hardcoded bootnodes ENRs in addition to DNS Discovery URLs as a way to overcome nameserver issues. Use a static shard instead of the default pubsub topic. Update tool to crawl and discover nodes via discv5.
• next: fix if necessary strange behavior with discv5 when ENRs in DNS discovery URL do not contain shards. Document steps for dogfooding.

[fryorcraken]

@richard-ramos shared instructions on how to run Status Desktop with static sharding: https://discord.com/channels/1110799176264056863/1166125031793901589/1166125169480306708 (Waku Discord - private channel)

[richard-ramos]

Weekly Update

• achieved: unsuccesfully tried to avoid introducing a breaking change in status-go. We need to decide whether to go ahead and merge that PR
• blocker: discv5 filters out outdated ENR entries from DNS Discovery URL in shard fleet - bug: can't discover peers when using DNS Discovery URL + shards nwaku#2162

[richard-ramos]

Weekly Update

• achieved: fix in status-go to use correct unprotected pubsub topic for community point of contacts, added pubsub topic bridge feature to go-waku, stop filtering out bootnodes on discovery, minimize noise on logs when selecting peers and not having peers available.
• next: deploy bridge between default pubsub topic and shard 32

[richard-ramos]

Weekly Update

• achieved: deployed bridge between default pubsub topic and shard 32, added UseShardAsDefaultTopic node config option to indicate whether the client should use a shard or the default waku topic. Merged open status-go PRs related to sharding. Initial connection to peers + dns-discovery no longer blocks the login. Updated open status-desktop PR for dogfooding to take into account status-go latest sharding related changes.
• next: get feat: shards.test fleet status-im/status-desktop#12344 merged.

[richard-ramos]

Weekly Update

• achieved: logout / login freeze, fix request on correct pubsub topic, and add missing shard information on community invite
• next: dogfooding

[richard-ramos]

Weekly Update

• achieved: fix pubsub topic used for store queries, logic for finding free port when initializing torrent service, add back changes related to default shard that were reverted before, store clusterID in app database, refactor mailserver cycle to not require having an active connection to a store node
• next: dogfooding

[chaitanyaprem]

Weekly Update

• achieved: fix issue of using default clusterID as 16 for shards fleet, dogfooding of status-desktop with shards fleet, debug issues in connection to fleet. See dogfooding report
• next: continue dogfooding

[chaitanyaprem]

Interim report of dogfooding shards-fleet using status desktop by Waku Team

Summary & Observations

• 5 CCs have participated in dogfooding the sharding fleet using various desktop builds (mac-aarch64, windows, linux)
• 2 test Communities were created and assigned shards where participants have joined and sent messages and verified history retrieval. 1:1 messages were tested by various participants.
• Peer connectivity was verified to ensure healthy peer connections for the shard
• Fetching message history for community before a user joined
• Identified and fixed issues in status-go to work with sharding fleet (Refer below)
• Raised an issue wrt fleet config that is causing desktop not to connect with different store nodes Update dns discovery url for shards.test status-im/infra-status#23
• Continue dogfooding once fleet config isssue is addressed

Issues observed/Raised in status desktop

• Desktop login failure status-im/status-desktop#12831
• Desktop keeps crashing when a different build is used for dogfooding status-fleet status-im/status-desktop#12807

UI related

• Node Management window is not vertically scrollable status-im/status-desktop#12746
• Suggested improvements to the layout of Node Management screen status-im/status-desktop#12745
• JSON-RPC window fully occupied by the results of a previous command status-im/status-desktop#12744
• JSON-RPC window is not scrollable status-im/status-desktop#12743
• Version links on About screen lead to unavailable Github pages status-im/status-desktop#12742
• Notification counter doesn't reset status-im/status-desktop#12741
• Checking seed phrase backup requires full words when 4 letters suffice status-im/status-desktop#12740
• Seed phrase: columns too wide apart status-im/status-desktop#12738

Issues resolved in status-go

• chore: add cluster_id to DB, move clusterID to config file and load clusterID when switching fleets status-im/status-go#4370
• fix: specify clusterid as 16 when using sharding fleet  status-im/status-go#4368
• fix: find free port for torrent status-im/status-go#4363
• fix: use default waku topic if pubsub topic is empty in store query status-im/status-go#4362

[richard-ramos]

Weekly Update

• achieved: troubleshoot / fix issues reported by QA on sharding PR
• next: continue dogfooding / fixing issues

[richard-ramos]

Weekly Update

• achieved: fix peer manager to take into account the ENR seq to determine if a peer is new or not and fix incorrect number of connected peers per topic. Register lightpush protocol correctly in go-waku. Drop pubsub topic bridging. Use shards.test fleet as default (in status-go and desktop)
• next: continue dogfooding / fixing issues

[chaitanyaprem]

Weekly Update

• achieved: status dogfooding, raise issues and optimizations needed wrt light protocols usage in status-go and improvements to be done in nwaku

[richard-ramos]

Weekly Update

• achieved: fix panic on logout, publish messages async, fix loading message history for communities, fix invalid bootnodes being used on status desktop.
• next: continue dogfooding / fixing issues

[chaitanyaprem]

Weekly Update

• achieved: analyze and repro filter delay issue reported in mobile e2e automated test by dogfooding
• next: continue status-mobile dogfooding with desktop / fixing issues

[richard-ramos]

Weekly Update

• achieved: attempt to identify root cause of filter delay issue, work on upgrading status-go to use Go 1.21 (to use latest go-libp2p), use latest go-waku version and identify missing commits between release and develop branch
• next: continue dogfooding / fixing issues

[chaitanyaprem]

Weekly Update

• achieved: status-mobile dogfooding, debug and attempt to identify root cause of filter delay issue
• next: continue dogfooding / fixing issues

[fryorcraken]

Waku dogfooding has concluded and Status QA has taken over testing.
Waku team is now providing support to Status testing.