0bc415c683
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. |
||
|---|---|---|
| .. | ||
| ann_validation.go | ||
| bootstrapper.go | ||
| gossiper_test.go | ||
| gossiper.go | ||
| log.go | ||
| syncer_test.go | ||
| syncer.go | ||
| utils.go | ||