lnd/discovery
Olaoluwa Osuntokun 206ad69b75
discovery: fix incorrect test, masked by loop scoping bug
When we first go to boot up the syncer, when we're in the active phase,
after we do the historical sync, we'll send a timestamp message that we
want everything, then transition to the passive mode. The test didn't
account for this extra message before, as the last test was being
re-used here (ran in parallel).

We fix this by asserting that the first expected message is sent, then
also the follow up messages as well.
2023-10-24 18:40:53 -07:00
..
bootstrapper.go multi: fix make fmt 2022-08-23 22:10:24 +08:00
chan_series.go discovery: fix incorrect test, masked by loop scoping bug 2023-10-24 18:40:53 -07:00
gossiper_test.go multi/refactor: separate methods for get and set node announcement 2023-05-04 10:35:42 -04:00
gossiper.go multi: add debug logs to catch slow shutdown 2023-10-06 16:34:47 -07:00
log.go multi: init subsystem loggers via build pkg 2018-10-05 13:04:45 +09:00
message_store_test.go discovery: use T.TempDir to create temporary test directory 2022-08-24 08:58:16 +08:00
message_store.go multi: add more trace logs regarding link activate flow 2023-03-21 10:18:49 +07:00
mock_test.go funding+peer: add support for new musig2 channel funding flow 2023-08-22 16:32:07 -07:00
reliable_sender_test.go multi: use btcd's btcec/v2 and btcutil modules 2022-03-09 19:02:37 +01:00
reliable_sender.go discovery+peer: add logs to reveal shutdown flow 2022-12-08 17:57:01 +08:00
sync_manager_test.go multi: use btcd's btcec/v2 and btcutil modules 2022-03-09 19:02:37 +01:00
sync_manager.go discovery+peer: add logs to reveal shutdown flow 2022-12-08 17:57:01 +08:00
syncer_test.go discovery: fix incorrect test, masked by loop scoping bug 2023-10-24 18:40:53 -07:00
syncer.go discovery+server: add more trace log 2023-03-08 21:02:53 +08:00