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
It seems that peer:identify kicks in later so that when js-waku has already a connection - it usually not negotiated fully so waitForPeers starts waiting for new peer:identify events
If it is the case that means that:
if waitForPeers is used - it will block execution unless there are more than one node present;
if waitForPeers is not used but subscription is getting initiated right after dial / bootstrap of the node - it might not have peers / protocols populated at that point in time (see picture);
Problem
When
js-waku
tab is open for first time sometimes Filter doesn't workSolution
Investigate and fix
The text was updated successfully, but these errors were encountered: