lnd/discovery
Johan T. Halseth 0bc415c683
discovery/gossiper: don't return on errChan for ChannelUpdate not yet processed
Previosuly we would immediately return nil on the error channel for
premature ChannelUpdates, which would break the expection that a a
returned non-error meant the update was successfully added to the
database. This meant that the caller would believe the update was added
to the database, while it is actually still in volatile memory and can
be lost during restarts.

This change makes us handle premature ChannelUpdates as we handle other
premature announcements within the gossiper, by deferring sending on the
error channel until we have reprocessed the update.
2018-08-23 07:40:40 +02:00
..
ann_validation.go multi: sort import paths with gofmt 2018-08-02 18:20:49 -07:00
bootstrapper.go multi: sort import paths with gofmt 2018-08-02 18:20:49 -07:00
gossiper_test.go discovery/gossiper: don't return on errChan for ChannelUpdate not yet processed 2018-08-23 07:40:40 +02:00
gossiper.go discovery/gossiper: don't return on errChan for ChannelUpdate not yet processed 2018-08-23 07:40:40 +02:00
log.go lnd: remove seelog logger 2017-06-25 14:19:56 +01:00
syncer_test.go discovery/syncer: store chunk size within gossiperSyncerCfg 2018-07-30 13:49:36 -07:00
syncer.go discovery/syncer: store chunk size within gossiperSyncerCfg 2018-07-30 13:49:36 -07:00
utils.go multi: sort import paths with gofmt 2018-08-02 18:20:49 -07:00