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
The order in which protocols are mounted, nodes are started, and peerInfo is retrieved; matters for peerInfo.protocols consistency
Impact
Low
To reproduce
The simplest way to reproduce is to checkout the test-peer-connection-management branch. Open tests/node/test_wakunode_peer_manager.nim and check out the Mount Order suite. In there there's a test case for each of the order possibilities. In the last two (info-start-protocol, info-protocol-start) the peerInfo is not updated with the correct protocols.
Problem
The order in which protocols are mounted, nodes are started, and peerInfo is retrieved; matters for peerInfo.protocols consistency
Impact
Low
To reproduce
The simplest way to reproduce is to checkout the
test-peer-connection-management
branch. Opentests/node/test_wakunode_peer_manager.nim
and check out theMount Order
suite. In there there's a test case for each of the order possibilities. In the last two (info-start-protocol
,info-protocol-start
) thepeerInfo
is not updated with the correct protocols.Expected behavior
Not sure if this is expected or not.
nwaku version/commit hash
The text was updated successfully, but these errors were encountered: