b884e1ceca
* Fix order of network streams When fetching a message from the network, we need to first listen for incoming messages and then look at the storage. If we do this in the opposite order, there's a brief moment where we've freezed our view of stored messages and are not yet listening for incoming ones, thus risking loosing messages. * Wait for waku db spurious delays Sometimes waku takes some time (e.g. a few seconds) before making a received message available through the archive query. Let's account for this by making repeated calls if the first one is not successful. * Add initial network wait We've observed in testing that even if waku reports that some peers are connected it can't really deliver a message. To overcome this limitation, we add a wait at the network service startup. We know this is not ideal, but Waku will eventually be replaced and we're looking for a quick fix. * fmt |
||
|---|---|---|
| .. | ||
| src | ||
| Cargo.toml | ||