6a9b96122d
In this commit we fix in a bug in `lnd` that could cause other implementations which implement a strict version of the spec to disconnect when trying to sync their channel graph using the gossip query feature. Before this commit, we would embed the request to a `QueryChannelRange` in the response, causing some clients to reject the response as the `FirstBlockHeight` and `NumBlocks` field would be identical for each chunk of the response. In order to remedy this, we now properly set these two fields with each returned chunk. Note that even after this commit, we keep our existing behavior surrounding the `Complete` field as is. Otherwise, current `lnd` clients which rely on this field (rather than the two aforementioned fields) wouldn't be able to properly detect when a set of responses to their query was "complete". Partially fixes #3728. |
||
|---|---|---|
| .. | ||
| bootstrapper.go | ||
| chan_series.go | ||
| gossiper_test.go | ||
| gossiper.go | ||
| log.go | ||
| message_store_test.go | ||
| message_store.go | ||
| mock_test.go | ||
| reliable_sender_test.go | ||
| reliable_sender.go | ||
| sync_manager_test.go | ||
| sync_manager.go | ||
| syncer_test.go | ||
| syncer.go | ||
| utils.go | ||