Connection state
  ✅ `waku:online` between 2 js-waku relay nodes
  ✅ isConnected between 2 js-waku relay nodes
  ✅ isConnected return false after peer stops
  ✅ isConnected should return false after all peers disconnect
  ✅ isConnected should return true after first peer connects
  ✅ should emit `waku:offline` event only when all peers disconnect
  ✅ should emit `waku:online` event only when first peer is connected

Dials attemptDial method
  ✅ should be called at least once on all `peer:discovery` events
Dials dialPeer method For bootstrap peers
  ✅ should be called for bootstrap peers
  ✅ should not be called more than DEFAULT_MAX_BOOTSTRAP_PEERS_ALLOWED times for bootstrap peers
Dials dialPeer method For peer-exchange peers
  ✅ should be called for every peer with PEER_EXCHANGE tags
  ✅ should be called for peers with PEER_EXCHANGE tags

Events peer:connect
  ✅ should emit `peer:connected:bootstrap` event when a peer is connected
  ✅ should emit `peer:connected:peer-exchange` event when a peer is connected
Events peer:discovery
  ✅ should emit `peer:discovery:bootstrap` event when a peer is discovered
  ✅ should emit `peer:discovery:peer-exchange` event when a peer is discovered
Events waku:connection
  ✅ should be online or offline if network state changed
  ✅ should emit events and trasition isConnected state when has peers or no peers

Public methods
  ✅ addEventListener with correct event
  ✅ addEventListener with wrong event
  ✅ dispatchEvent via connectionManager
  ✅ getPeersByDiscovery
  ✅ listenerCount
  ✅ removeEventListener with correct event
  ✅ removeEventListener with wrong event
  ✅ safeDispatchEvent
  ✅ stop

DNS Discovery: Compliance Test interface-peer-discovery compliance tests
  ✅ can start and stop the service
  ✅ can start the service
  ✅ should emit a peer event after start
  ✅ should not fail to start the service if it is already started
  ✅ should not fail to stop the service if it was not started
  ✅ should not receive a peer event after stop
  ✅ should not receive a peer event before start
DNS Node Discovery [live data]
  ⚪ passes more than one ENR URLs and attempts connection
  ⚪ should retrieve 3 multiaddrs for test.waku.nodes.status.im
  ⚪ should use DNS peer discovery with light client

ENR Interop: ServiceNode
  ✅ All
  ✅ Relay
  ✅ Relay + Store

Waku Message Ephemeral field
  ✅ Ephemeral field is preserved - asymmetric encryption
  ✅ Ephemeral field is preserved - encoder v0
  ✅ Ephemeral field is preserved - symmetric encryption
  ✅ Ephemeral messages are not stored

Waku Filter V2: Ping: Multiple Nodes: Strict Checking: false
  ✅ Ping on peer without subscriptions
  ✅ Ping on subscribed peer
  ✅ Ping on unsubscribed peer
  ✅ Reopen subscription with peer with lost subscription
Waku Filter V2: Ping: Multiple Nodes: Strict Checking: true
  ✅ Ping on peer without subscriptions
  ✅ Ping on subscribed peer
  ✅ Ping on unsubscribed peer
  ✅ Reopen subscription with peer with lost subscription

Waku Filter V2: FilterPush: Multiple Nodes: Strict Checking: false
  ✅ Check message on other pubsub topic is not received
  ⚪ Check message received after jswaku node is restarted
  ⚪ Check message received after nwaku node is restarted
  ✅ Check message with invalid timestamp is not received
  ✅ Check message with no content topic is not received
  ✅ Check message with no payload is not received
  ✅ Check message with non string payload is not received
  ✅ Check received message containing Arabic
  ✅ Check received message containing Basic HTML tag
  ✅ Check received message containing Chinese
  ✅ Check received message containing emoji
  ✅ Check received message containing escaped characters
  ✅ Check received message containing JSON
  ✅ Check received message containing long
  ✅ Check received message containing numeric
  ✅ Check received message containing Russian
  ✅ Check received message containing Script
  ✅ Check received message containing shell command
  ✅ Check received message containing short
  ✅ Check received message containing special chars
  ✅ Check received message containing SQL Injection
  ✅ Check received message containing unicode special characters
  ✅ Check received message containing XML
  ✅ Check received message with timestamp: 1649153314 
  ✅ Check received message with timestamp: 1738344946919 
  ✅ Check received message with timestamp: 1738344946919000000 
  ✅ Check received message with timestamp: 1949153314000 
Waku Filter V2: FilterPush: Multiple Nodes: Strict Checking: true
  ✅ Check message on other pubsub topic is not received
  ⚪ Check message received after jswaku node is restarted
  ⚪ Check message received after nwaku node is restarted
  ✅ Check message with invalid timestamp is not received
  ✅ Check message with no content topic is not received
  ✅ Check message with no payload is not received
  ✅ Check message with non string payload is not received
  ✅ Check received message containing Arabic
  ✅ Check received message containing Basic HTML tag
  ✅ Check received message containing Chinese
  ✅ Check received message containing emoji
  ✅ Check received message containing escaped characters
  ✅ Check received message containing JSON
  ✅ Check received message containing long
  ✅ Check received message containing numeric
  ✅ Check received message containing Russian
  ✅ Check received message containing Script
  ✅ Check received message containing shell command
  ✅ Check received message containing short
  ✅ Check received message containing special chars
  ✅ Check received message containing SQL Injection
  ✅ Check received message containing unicode special characters
  ✅ Check received message containing XML
  ✅ Check received message with timestamp: 1649153314 
  ✅ Check received message with timestamp: 1738344946919 
  ✅ Check received message with timestamp: 1738344946919000000 
  ✅ Check received message with timestamp: 1949153314000 

Waku Filter V2 (Autosharding): Multiple PubsubTopics
  ✅ Should fail to subscribe with decoder with wrong pubsubTopic
  ✅ Subscribe and receive messages from 2 nwaku nodes each with different pubsubtopics
  ✅ Subscribe and receive messages on 2 different pubsubtopics
  ✅ Subscribe and receive messages on autosharded pubsubtopic
Waku Filter V2 (Named sharding): Multiple PubsubTopics
  ✅ Should fail to subscribe with decoder with wrong pubsubTopic
  ✅ Subscribe and receive messages from 2 nwaku nodes each with different pubsubtopics
  ✅ Subscribe and receive messages on 2 different pubsubtopics
  ✅ Subscribe and receive messages on custom pubsubtopic
Waku Filter V2: Multiple PubsubTopics
  ✅ Subscribe and receive messages from 2 nwaku nodes each with different pubsubtopics
  ✅ Subscribe and receive messages on 2 different pubsubtopics
  ✅ Subscribe and receive messages on custom pubsubtopic

Waku Filter V2: Ping
  ✅ Ping on peer without subscriptions
  ✅ Ping on subscribed peer
  ✅ Ping on unsubscribed peer
  ✅ Reopen subscription with peer with lost subscription

Waku Filter V2: FilterPush
  ✅ Check message on other pubsub topic is not received
  ⚪ Check message received after jswaku node is restarted
  ⚪ Check message received after nwaku node is restarted
  ✅ Check message with invalid timestamp is not received
  ✅ Check message with no content topic is not received
  ✅ Check message with no payload is not received
  ✅ Check message with no pubsub topic is not received
  ✅ Check message with non string payload is not received
  ✅ Check received message containing Arabic
  ✅ Check received message containing Basic HTML tag
  ✅ Check received message containing Chinese
  ✅ Check received message containing emoji
  ✅ Check received message containing escaped characters
  ✅ Check received message containing JSON
  ✅ Check received message containing long
  ✅ Check received message containing numeric
  ✅ Check received message containing Russian
  ✅ Check received message containing Script
  ✅ Check received message containing shell command
  ✅ Check received message containing short
  ✅ Check received message containing special chars
  ✅ Check received message containing SQL Injection
  ✅ Check received message containing unicode special characters
  ✅ Check received message containing XML
  ✅ Check received message with timestamp: 1649153314 
  ✅ Check received message with timestamp: 1738344947316 
  ✅ Check received message with timestamp: 1738344947316000000 
  ✅ Check received message with timestamp: 1949153314000 

Waku Filter V2: Subscribe: Single Service Node
  ✅ Add multiple subscription objects on single nwaku node
  ✅ Error when try to subscribe to more than 101 topics (new limit)
  ✅ Overlapping topic subscription
  ✅ Refresh subscription
  ✅ Subscribe and receive 2 messages on the same topic
  ✅ Subscribe and receive ecies encrypted messages via lightPush
  ✅ Subscribe and receive messages from multiple nwaku nodes
  ✅ Subscribe and receive messages on 2 different content topics
  ✅ Subscribe and receive messages via lightPush
  ✅ Subscribe and receive messages via waku relay post
  ✅ Subscribe and receive symmetrically encrypted messages via lightPush
  ✅ Subscribe and receives messages on 20 topics
  ✅ Subscribe to 100 topics (new limit) at once and receives messages
  ✅ Subscribe to topic containing Arabic and receive message
  ✅ Subscribe to topic containing Basic HTML tag and receive message
  ✅ Subscribe to topic containing Chinese and receive message
  ✅ Subscribe to topic containing emoji and receive message
  ✅ Subscribe to topic containing escaped characters and receive message
  ✅ Subscribe to topic containing JSON and receive message
  ✅ Subscribe to topic containing long and receive message
  ✅ Subscribe to topic containing numeric and receive message
  ✅ Subscribe to topic containing Russian and receive message
  ✅ Subscribe to topic containing Script and receive message
  ✅ Subscribe to topic containing shell command and receive message
  ✅ Subscribe to topic containing short and receive message
  ✅ Subscribe to topic containing special chars and receive message
  ✅ Subscribe to topic containing SQL Injection and receive message
  ✅ Subscribe to topic containing unicode special characters and receive message
  ✅ Subscribe to topic containing XML and receive message

Waku Filter V2: Unsubscribe
  ✅ Unsubscribe 1 topic - node subscribed to 1 topic
  ✅ Unsubscribe 1 topic - node subscribed to 2 topics
  ✅ Unsubscribe 2 topics - node subscribed to 2 topics
  ✅ Unsubscribe topics the node is not subscribed to
  ✅ Unsubscribes all - node subscribed to 1 topic
  ✅ Unsubscribes all - node subscribed to 10 topics

Waku Filter V2: Subscribe: Multiple Service Nodes: Strict Check mode: false
  ✅ Add multiple subscription objects on single nwaku node
  ✅ Error when try to subscribe to more than 101 topics (new limit)
  ✅ Overlapping topic subscription
  ✅ Refresh subscription
  ✅ Renews subscription after lossing a connection
  ✅ Subscribe and receive 2 messages on the same topic
  ✅ Subscribe and receive ecies encrypted messages via lightPush
  ✅ Subscribe and receive messages on 2 different content topics
  ✅ Subscribe and receive messages via lightPush
  ✅ Subscribe and receive messages via waku relay post
  ✅ Subscribe and receive symmetrically encrypted messages via lightPush
  ✅ Subscribe and receives messages on 20 topics
  ✅ Subscribe to 100 topics (new limit) at once and receives messages
  ✅ Subscribe to topic containing Arabic and receive message
  ✅ Subscribe to topic containing Basic HTML tag and receive message
  ✅ Subscribe to topic containing Chinese and receive message
  ✅ Subscribe to topic containing emoji and receive message
  ✅ Subscribe to topic containing escaped characters and receive message
  ✅ Subscribe to topic containing JSON and receive message
  ✅ Subscribe to topic containing long and receive message
  ✅ Subscribe to topic containing numeric and receive message
  ✅ Subscribe to topic containing Russian and receive message
  ✅ Subscribe to topic containing Script and receive message
  ✅ Subscribe to topic containing shell command and receive message
  ✅ Subscribe to topic containing short and receive message
  ✅ Subscribe to topic containing special chars and receive message
  ✅ Subscribe to topic containing SQL Injection and receive message
  ✅ Subscribe to topic containing unicode special characters and receive message
  ✅ Subscribe to topic containing XML and receive message
Waku Filter V2: Subscribe: Multiple Service Nodes: Strict Check mode: true
  ✅ Add multiple subscription objects on single nwaku node
  ✅ Error when try to subscribe to more than 101 topics (new limit)
  ✅ Overlapping topic subscription
  ✅ Refresh subscription
  ✅ Renews subscription after lossing a connection
  ✅ Subscribe and receive 2 messages on the same topic
  ✅ Subscribe and receive ecies encrypted messages via lightPush
  ✅ Subscribe and receive messages on 2 different content topics
  ✅ Subscribe and receive messages via lightPush
  ✅ Subscribe and receive messages via waku relay post
  ✅ Subscribe and receive symmetrically encrypted messages via lightPush
  ✅ Subscribe and receives messages on 20 topics
  ✅ Subscribe to 100 topics (new limit) at once and receives messages
  ✅ Subscribe to topic containing Arabic and receive message
  ✅ Subscribe to topic containing Basic HTML tag and receive message
  ✅ Subscribe to topic containing Chinese and receive message
  ✅ Subscribe to topic containing emoji and receive message
  ✅ Subscribe to topic containing escaped characters and receive message
  ✅ Subscribe to topic containing JSON and receive message
  ✅ Subscribe to topic containing long and receive message
  ✅ Subscribe to topic containing numeric and receive message
  ✅ Subscribe to topic containing Russian and receive message
  ✅ Subscribe to topic containing Script and receive message
  ✅ Subscribe to topic containing shell command and receive message
  ✅ Subscribe to topic containing short and receive message
  ✅ Subscribe to topic containing special chars and receive message
  ✅ Subscribe to topic containing SQL Injection and receive message
  ✅ Subscribe to topic containing unicode special characters and receive message
  ✅ Subscribe to topic containing XML and receive message

Waku Filter V2: Unsubscribe: Multiple Nodes: Strict Checking: false
  ✅ Unsubscribe 1 topic - node subscribed to 1 topic
  ✅ Unsubscribe 1 topic - node subscribed to 2 topics
  ✅ Unsubscribe 2 topics - node subscribed to 2 topics
  ✅ Unsubscribe topics the node is not subscribed to
  ✅ Unsubscribes all - node subscribed to 1 topic
  ✅ Unsubscribes all - node subscribed to 10 topics
Waku Filter V2: Unsubscribe: Multiple Nodes: Strict Checking: true
  ✅ Unsubscribe 1 topic - node subscribed to 1 topic
  ✅ Unsubscribe 1 topic - node subscribed to 2 topics
  ✅ Unsubscribe 2 topics - node subscribed to 2 topics
  ✅ Unsubscribe topics the node is not subscribed to
  ✅ Unsubscribes all - node subscribed to 1 topic
  ✅ Unsubscribes all - node subscribed to 10 topics

Node Health Status Matrix Tests
  ⚪ LightPush: 0 peers, Filter: 0 peers
  ⚪ LightPush: 0 peers, Filter: 1 peers
  ⚪ LightPush: 0 peers, Filter: 2 peers
  ⚪ LightPush: 0 peers, Filter: 3 peers
  ⚪ LightPush: 1 peers, Filter: 0 peers
  ⚪ LightPush: 1 peers, Filter: 1 peers
  ⚪ LightPush: 1 peers, Filter: 2 peers
  ⚪ LightPush: 1 peers, Filter: 3 peers
  ⚪ LightPush: 2 peers, Filter: 0 peers
  ⚪ LightPush: 2 peers, Filter: 1 peers
  ⚪ LightPush: 2 peers, Filter: 2 peers
  ⚪ LightPush: 2 peers, Filter: 3 peers
  ⚪ LightPush: 3 peers, Filter: 0 peers
  ⚪ LightPush: 3 peers, Filter: 1 peers
  ⚪ LightPush: 3 peers, Filter: 2 peers
  ⚪ LightPush: 3 peers, Filter: 3 peers

Health Manager Should update the health status for protocols
  ⚪ Filter with 0 connections
  ⚪ Filter with 1 connections
  ⚪ Filter with 2 connections
  ⚪ Filter with 3 connections
  ⚪ LightPush with 0 connections
  ⚪ LightPush with 1 connections
  ⚪ LightPush with 2 connections
  ⚪ LightPush with 3 connections

Waku Light Push: Multiple Nodes: Strict Check: true
  ❌ "before each" hook for "Push message with meta"
	Timeout of 50000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/home/runner/work/nwaku/nwaku/packages/tests/tests/light-push/index.node.spec.ts)
  ✅ Fails to push message with empty content topic
  ❌ Push 30 different messages
	expected +0 to equal 2
  ❌ Push message with Arabic payload
	expected +0 to equal 2
  ❌ Push message with Basic HTML tag payload
	expected +0 to equal 2
  ❌ Push message with Chinese payload
	expected +0 to equal 2
  ❌ Push message with content topic containing Arabic
	expected +0 to equal 2
  ❌ Push message with content topic containing Basic HTML tag
	expected +0 to equal 2
  ❌ Push message with content topic containing Chinese
	expected +0 to equal 2
  ❌ Push message with content topic containing emoji
	expected +0 to equal 2
  ❌ Push message with content topic containing escaped characters
	expected +0 to equal 2
  ❌ Push message with content topic containing JSON
	expected +0 to equal 2
  ❌ Push message with content topic containing long
	expected +0 to equal 2
  ❌ Push message with content topic containing numeric
	expected +0 to equal 2
  ❌ Push message with content topic containing Russian
	expected +0 to equal 2
  ❌ Push message with content topic containing Script
	expected +0 to equal 2
  ❌ Push message with content topic containing shell command
	expected +0 to equal 2
  ❌ Push message with content topic containing short
	expected +0 to equal 2
  ❌ Push message with content topic containing special chars
	expected +0 to equal 2
  ❌ Push message with content topic containing SQL Injection
	expected +0 to equal 2
  ❌ Push message with content topic containing unicode special characters
	expected +0 to equal 2
  ❌ Push message with content topic containing XML
	expected +0 to equal 2
  ❌ Push message with emoji payload
	expected +0 to equal 2
  ❌ Push message with escaped characters payload
	expected +0 to equal 2
  ❌ Push message with JSON payload
	expected +0 to equal 2
  ❌ Push message with long payload
	expected +0 to equal 2
  ❌ Push message with numeric payload
	expected +0 to equal 2
  ❌ Push message with Russian payload
	expected +0 to equal 2
  ❌ Push message with Script payload
	expected +0 to equal 2
  ❌ Push message with shell command payload
	expected +0 to equal 2
  ❌ Push message with short payload
	expected +0 to equal 2
  ❌ Push message with special chars payload
	expected +0 to equal 2
  ❌ Push message with SQL Injection payload
	expected +0 to equal 2
  ❌ Push message with unicode special characters payload
	expected +0 to equal 2
  ❌ Push message with XML payload
	expected +0 to equal 2
  ✅ Throws when trying to push message with empty payload

Waku Light Push: Single Node
  ✅ Fails to push message bigger that 1MB
  ✅ Fails to push message with empty content topic
  ✅ Fails to push message with large meta
  ❌ Push 30 different messages
	expected +0 to equal 1
  ❌ Push message equal or less that 1MB
	expected +0 to be above +0
  ❌ Push message with Arabic payload
	expected +0 to equal 1
  ❌ Push message with Basic HTML tag payload
	expected +0 to equal 1
  ❌ Push message with Chinese payload
	expected +0 to equal 1
  ❌ Push message with content topic containing Arabic
	expected +0 to equal 1
  ❌ Push message with content topic containing Basic HTML tag
	expected +0 to equal 1
  ❌ Push message with content topic containing Chinese
	expected +0 to equal 1
  ❌ Push message with content topic containing emoji
	expected +0 to equal 1
  ❌ Push message with content topic containing escaped characters
	expected +0 to equal 1
  ❌ Push message with content topic containing JSON
	expected +0 to equal 1
  ❌ Push message with content topic containing long
	expected +0 to equal 1
  ❌ Push message with content topic containing numeric
	expected +0 to equal 1
  ❌ Push message with content topic containing Russian
	expected +0 to equal 1
  ❌ Push message with content topic containing Script
	expected +0 to equal 1
  ❌ Push message with content topic containing shell command
	expected +0 to equal 1
  ❌ Push message with content topic containing short
	expected +0 to equal 1
  ❌ Push message with content topic containing special chars
	expected +0 to equal 1
  ❌ Push message with content topic containing SQL Injection
	expected +0 to equal 1
  ❌ Push message with content topic containing unicode special characters
	expected +0 to equal 1
  ❌ Push message with content topic containing XML
	expected +0 to equal 1
  ❌ Push message with custom timestamp: 1707586678255
	expected +0 to equal 1
  ❌ Push message with custom timestamp: 1738341478255
	expected +0 to equal 1
  ❌ Push message with custom timestamp: 1738348678255
	expected +0 to equal 1
  ❌ Push message with emoji payload
	expected +0 to equal 1
  ❌ Push message with escaped characters payload
	expected +0 to equal 1
  ❌ Push message with JSON payload
	expected +0 to equal 1
  ❌ Push message with long payload
	expected +0 to equal 1
  ❌ Push message with meta
	expected +0 to equal 1
  ❌ Push message with numeric payload
	expected +0 to equal 1
  ❌ Push message with rate limit
	expected +0 to equal 1
  ❌ Push message with Russian payload
	expected +0 to equal 1
  ❌ Push message with Script payload
	expected +0 to equal 1
  ❌ Push message with shell command payload
	expected +0 to equal 1
  ❌ Push message with short payload
	expected +0 to equal 1
  ❌ Push message with special chars payload
	expected +0 to equal 1
  ❌ Push message with SQL Injection payload
	expected +0 to equal 1
  ❌ Push message with unicode special characters payload
	expected +0 to equal 1
  ❌ Push message with XML payload
	expected +0 to equal 1
  ✅ Throws when trying to push message with empty payload

Waku Light Push : Multiple PubsubTopics
  ✅ Light push messages to 2 nwaku nodes each with different pubsubtopics
  ❌ Push message on custom pubsubTopic
	Cannot read properties of undefined (reading 'toString')
  ❌ Subscribe and receive messages on 2 different pubsubtopics
	Cannot read properties of undefined (reading 'toString')
Waku Light Push (Autosharding): Multiple PubsubTopics
  ✅ Light push messages to 2 nwaku nodes each with different pubsubtopics
  ❌ Push message on custom pubsubTopic
	expected [ { …(2) } ] to be empty
  ❌ Subscribe and receive messages on 2 different pubsubtopics
	Cannot read properties of undefined (reading 'toString')
Waku Light Push (named sharding): Multiple PubsubTopics
  ❌ Light push messages to 2 nwaku nodes each with different pubsubtopics
	expected [ { …(2) }, { …(2) } ] to be empty
  ❌ Push message on custom pubsubTopic
	Cannot read properties of undefined (reading 'toString')
  ❌ Subscribe and receive messages on 2 different pubsubtopics
	Cannot read properties of undefined (reading 'toString')

This Is
  ✅ A test
This Is also
  ✅ A test

Metadata Protocol
  ✅ PeerStore has remote peer's shard info after successful connection
  ✅ receiving a ping from a peer does not overwrite shard info
Metadata Protocol connections
  ✅ different cluster, different shard: nodes don't connect
  ✅ different cluster, same shard: nodes don't connect
  ✅ same cluster, different shard: nodes connect
  ✅ same cluster, same shard: nodes connect

multiaddr: dialing
  ✅ can dial TLS multiaddrs
multiaddr: dialing does not attempt the same peer discovered multiple times more than once
  ✅ through manual discovery

nwaku
  ✅ Correctly serialized arguments

Peer Exchange Compliance Test interface-peer-discovery compliance tests
  ✅ can start and stop the service
  ✅ can start the service
  ✅ should emit a peer event after start
  ✅ should not fail to start the service if it is already started
  ✅ should not fail to stop the service if it was not started
  ✅ should not receive a peer event after stop
  ✅ should not receive a peer event before start

Peer Exchange Continuous Discovery
  ✅ Should update multiaddrs
  ✅ Should update shard info

Peer Exchange
  ✅ getPeersByDiscovery
  ⚪ new peer added after a peer was already found
  ✅ peerDiscovery without wakuPeerExchangeDiscovery
  ⚪ wrong wakuPeerExchangeDiscovery pubsub topic

Peer Exchange Query
  ⚪ connected peers and dial
  ⚪ less peers than existing
  ⚪ more peers than existing
  ⚪ non connected peers

Waku Relay
  ✅ Decrypt messages
  ✅ Delete observer

Waku Relay, Interop
  ✅ Js publishes, other Js receives
  ✅ Nwaku publishes
  ✅ nwaku subscribes
  ✅ Publishes to nwaku

Waku Relay (Autosharding), multiple pubsub topics
  ✅ 3 nodes on /waku/2/rs/7/0 topic
  ✅ 3 nodes on /waku/2/rs/7/1 topic
  ✅ n1 and n2 uses a custom pubsub, n3 uses the default pubsub
  ✅ Nodes with multiple pubsub topic
Waku Relay, multiple pubsub topics
  ✅ 3 nodes on /waku/2/rs/3/1 topic
  ✅ 3 nodes on /waku/2/rs/3/2 topic
  ✅ n1 and n2 uses a custom pubsub, n3 uses the default pubsub
  ✅ Nodes with multiple pubsub topic

Waku Relay, Publish
  ⚪ Check publish message after client node is restarted
  ⚪ Check publish message after service node is restarted
  ✅ Check publish message containing Arabic
  ✅ Check publish message containing Basic HTML tag
  ✅ Check publish message containing Chinese
  ✅ Check publish message containing emoji
  ✅ Check publish message containing escaped characters
  ✅ Check publish message containing JSON
  ✅ Check publish message containing long
  ✅ Check publish message containing numeric
  ✅ Check publish message containing Russian
  ✅ Check publish message containing Script
  ✅ Check publish message containing shell command
  ✅ Check publish message containing short
  ✅ Check publish message containing special chars
  ✅ Check publish message containing SQL Injection
  ✅ Check publish message containing unicode special characters
  ✅ Check publish message containing XML
  ✅ Fails to publish duplicate message
  ✅ Fails to publish message with empty text
  ✅ Fails to publish message with size larger than 1 MB
  ✅ Fails to publish message with size larger than 1 MB
  ✅ Fails to publish message with wrong content topic
  ✅ Fails to publish message with wrong pubsubtopic
  ✅ Publish message with custom timestamp: Fri Jan 31 2025 16:40:28 GMT+0000 (Coordinated Universal Time)
  ✅ Publish message with custom timestamp: Fri Jan 31 2025 18:40:28 GMT+0000 (Coordinated Universal Time)
  ✅ Publish message with custom timestamp: Sat Feb 10 2024 17:40:28 GMT+0000 (Coordinated Universal Time)
  ✅ Publish message with custom timestamp: Sun Dec 17 1995 03:24:00 GMT+0000 (Coordinated Universal Time)
  ✅ Publish message with large meta
  ✅ Publish message with rate limit

Waku Relay, Subscribe
  ✅ Mutual subscription
  ⚪ Overlapping topic subscription
  ✅ Publish without waiting for remote peer
  ⚪ Refresh subscription
  ✅ Register correct protocols
  ✅ Subscribe and publish 10000 messages on the same topic
  ✅ Subscribe and publish message
  ✅ Subscribe and publish messages on 2 different content topics
  ✅ Subscribe at once to 10000 topics and publish messages
  ✅ Subscribe one by one to 100 topics and publish messages
  ✅ Subscribe to topic containing Arabic and publish message
  ✅ Subscribe to topic containing Basic HTML tag and publish message
  ✅ Subscribe to topic containing Chinese and publish message
  ✅ Subscribe to topic containing emoji and publish message
  ✅ Subscribe to topic containing escaped characters and publish message
  ✅ Subscribe to topic containing JSON and publish message
  ✅ Subscribe to topic containing long and publish message
  ✅ Subscribe to topic containing numeric and publish message
  ✅ Subscribe to topic containing Russian and publish message
  ✅ Subscribe to topic containing Script and publish message
  ✅ Subscribe to topic containing shell command and publish message
  ✅ Subscribe to topic containing short and publish message
  ✅ Subscribe to topic containing special chars and publish message
  ✅ Subscribe to topic containing SQL Injection and publish message
  ✅ Subscribe to topic containing unicode special characters and publish message
  ✅ Subscribe to topic containing XML and publish message

Autosharding: Running Nodes Different clusters and topics
  ❌ Cluster ID 0 - Default/Global Cluster
	expected +0 to equal 1
  ❌ Non TWN Cluster
	expected +0 to equal 1
  ❌ random auto sharding 1 - Cluster ID: 10, Content Topic: /app4/6/topic33/xml
	expected +0 to equal 1
  ❌ random auto sharding 10 - Cluster ID: 10, Content Topic: /app16/6/topic69/proto
	expected +0 to equal 1
  ❌ random auto sharding 2 - Cluster ID: 10, Content Topic: /app94/4/topic537/utf8
	expected +0 to equal 1
  ❌ random auto sharding 3 - Cluster ID: 10, Content Topic: /app90/4/topic87/utf8
	expected +0 to equal 1
  ❌ random auto sharding 4 - Cluster ID: 10, Content Topic: /app95/3/topic621/test.js
	expected +0 to equal 1
  ❌ random auto sharding 5 - Cluster ID: 10, Content Topic: /app51/2/topic360/utf8
	expected +0 to equal 1
  ❌ random auto sharding 6 - Cluster ID: 10, Content Topic: /app46/10/topic443/json
	expected +0 to equal 1
  ❌ random auto sharding 7 - Cluster ID: 10, Content Topic: /app36/10/topic975/test.js
	expected +0 to equal 1
  ❌ random auto sharding 8 - Cluster ID: 10, Content Topic: /app66/2/topic996/test.js
	expected +0 to equal 1
  ❌ random auto sharding 9 - Cluster ID: 10, Content Topic: /app47/7/topic409/test.js
	expected +0 to equal 1
  ✅ Wrong topic
Autosharding: Running Nodes Others
  ❌ configure the node with multiple content topics
	expected +0 to equal 1
  ✅ start node with empty content topic
  ✅ using a protocol with unconfigured pubsub topic should fail

Autosharding: Peer Management Peer Exchange
  ✅ all px service nodes subscribed to the shard topic should be dialed
  ✅ px service nodes not subscribed to the shard should not be dialed
Static Sharding: Peer Management Peer Exchange
  ✅ all px service nodes subscribed to the shard topic should be dialed
  ✅ px service nodes not subscribed to the shard should not be dialed

Static Sharding: Running Nodes Different clusters and shards
  ❌ Cluster ID 0 - Default/Global Cluster
	expected +0 to equal 1
  ❌ random static sharding 1 - Cluster ID: 90, Shard ID: 439
	expected +0 to equal 1
  ❌ random static sharding 10 - Cluster ID: 786, Shard ID: 236
	expected +0 to equal 1
  ❌ random static sharding 2 - Cluster ID: 457, Shard ID: 375
	expected +0 to equal 1
  ❌ random static sharding 3 - Cluster ID: 257, Shard ID: 736
	expected +0 to equal 1
  ❌ random static sharding 4 - Cluster ID: 915, Shard ID: 718
	expected +0 to equal 1
  ❌ random static sharding 5 - Cluster ID: 218, Shard ID: 775
	expected +0 to equal 1
  ❌ random static sharding 6 - Cluster ID: 172, Shard ID: 482
	expected +0 to equal 1
  ❌ random static sharding 7 - Cluster ID: 487, Shard ID: 826
	expected +0 to equal 1
  ❌ random static sharding 8 - Cluster ID: 615, Shard ID: 681
	expected +0 to equal 1
  ❌ random static sharding 9 - Cluster ID: 487, Shard ID: 929
	expected +0 to equal 1
  ❌ shard 0
	expected +0 to equal 1
Static Sharding: Running Nodes Others
  ❌ configure the node with multiple pubsub topics
	expected +0 to equal 1
  ✅ start node with empty shard should fail
  ✅ using a protocol with unconfigured pubsub topic should fail

Waku Store, cursor
  ✅ Passing a valid cursor at 0 index when there are 20 messages
  ✅ Passing a valid cursor at 10 index when there are 40 messages
  ✅ Passing a valid cursor at 110 index when there are 120 messages
  ✅ Passing a valid cursor at 19 index when there are 20 messages
  ✅ Passing a valid cursor at 19 index when there are 50 messages
  ✅ Passing a valid cursor at 2 index when there are 4 messages
  ✅ Passing cursor with wrong pubsubTopic
  ✅ Passing invalid cursor
  ✅ Reusing cursor across nodes

Waku Store, error handling
  ✅ Query Generator, Multiple PubsubTopics
  ✅ Query Generator, No Decoder
  ✅ Query Generator, No message returned
  ✅ Query Generator, Wrong PubsubTopic
  ✅ Query with Ordered Callback, Multiple PubsubTopics
  ✅ Query with Ordered Callback, No Decoder
  ✅ Query with Ordered Callback, No message returned
  ✅ Query with Ordered Callback, Wrong PubsubTopic
  ✅ Query with Promise Callback, Multiple PubsubTopics
  ✅ Query with Promise Callback, No Decoder
  ✅ Query with Promise Callback, No message returned
  ✅ Query with Promise Callback, Wrong PubsubTopic

Waku Store, general
  ✅ Callback on promise
  ✅ Callback on promise, aborts when callback returns true
  ✅ Generator, with asymmetric & symmetric encrypted messages
  ✅ Ordered callback, aborts when callback returns true
  ✅ Query generator for 2000 messages
  ✅ Query generator for multiple messages
  ✅ Query generator for multiple messages with different content topic format
  ✅ Query generator for multiple messages with different message text format
  ✅ Query generator for multiple messages with multiple decoders

Waku Store (Autosharding), custom pubsub topic
  ❌ Generator, 2 different pubsubtopics
	expected +0 to equal 10
  ❌ Generator, 2 nwaku nodes each with different pubsubtopics
	Timeout of 10000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/home/runner/work/nwaku/nwaku/packages/tests/tests/store/multiple_pubsub.spec.ts)
  ❌ Generator, custom pubsub topic
	expected +0 to equal 20
Waku Store (named sharding), custom pubsub topic
  ✅ Generator, 2 different pubsubtopics
  ✅ Generator, 2 nwaku nodes each with different pubsubtopics
  ✅ Generator, custom pubsub topic
Waku Store, custom pubsub topic
  ✅ Generator, 2 different pubsubtopics
  ✅ Generator, 2 nwaku nodes each with different pubsubtopics
  ✅ Generator, custom pubsub topic

Waku Store, order
  ✅ Ordered Callback - false
  ✅ Ordered Callback - true
  ✅ Promise Callback  - false
  ✅ Promise Callback  - true
  ✅ Query Generator  - false
  ✅ Query Generator  - true

Waku Store, page size
  ✅ Default pageSize
  ✅ Passing page size 0 when there are 110 messages
  ✅ Passing page size 1 when there are 4 messages
  ✅ Passing page size 10 when there are 10 messages
  ✅ Passing page size 11 when there are 10 messages
  ✅ Passing page size 110 when there are 120 messages
  ✅ Passing page size 19 when there are 20 messages
  ✅ Passing page size 3 when there are 20 messages

Waku Store, sorting
  ✅ Ordered Callback sorting by timestamp while page direction is false
  ✅ Ordered Callback sorting by timestamp while page direction is true
  ✅ Query Generator sorting by timestamp while page direction is false
  ✅ Query Generator sorting by timestamp while page direction is true

Waku Store, time filter
  ❌ msgTime: -19000 ms from now, startTime: -18990, endTime: -19010
	Store query failed with status code: 300, description: BAD_RESPONSE: archive error: INVALID_QUERY: startTime should be before endTime
  ✅ msgTime: -19000 ms from now, startTime: -18999, endTime: -18996
  ✅ msgTime: -19000 ms from now, startTime: -19000, endTime: -18000
  ✅ msgTime: -19000 ms from now, startTime: -19002, endTime: -19001
  ✅ msgTime: -19000 ms from now, startTime: -19010, endTime: -18990
  ✅ msgTime: -19000 ms from now, startTime: -20000, endTime: -19000
  ✅ msgTime: 19000 ms from now, startTime: 18990, endTime: 19010
  ✅ Timestamp too far from node time: -20000 ms from now
  ✅ Timestamp too far from node time: 40000 ms from now

Util: toAsyncIterator: Filter
  ✅ creates an iterator
  ✅ handles multiple messages
  ✅ unsubscribes

Wait for remote peer
  ✅ Filter
  ✅ Light Node - default protocols
  ✅ LightPush
  ✅ Privacy Node - default protocol
  ✅ Relay - dialed after
  ✅ Relay - dialed first
  ✅ Relay - times out
  ✅ Store - dialed after - with timeout
  ✅ Store - dialed first

Decryption Keys
  ✅ Used by Waku Relay
User Agent
  ✅ Sets default value correctly
Waku Dial [node only] Bootstrap
  ✅ Passing an array
  ✅ Using a function
Waku Dial [node only] Interop: ServiceNode
  ✅ connects to nwaku
  ✅ Does not throw an exception when node disconnects