[v0.21.x-branch] Backport #11035: lnwallet+lnwire: handle boundary cases - #11077
Merged
Conversation
Return both completion results when the reservation is no longer present. Add a focused regression test for the missing-reservation response. (cherry picked from commit 8bf173e)
Clamp zero-block range boundaries without treating them as valid empty ranges. Avoid emitting a zero-block prefix when the first queried block exceeds the reply chunk size, and cover both discovery paths. (cherry picked from commit b423c8b)
Document the channel funding and channel range boundary fixes for the v0.21.3 maintenance release. (cherry picked from commit 081adeb)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport of #11035
Summary
prefixes.
Change Description
The wallet funding handler now returns both completion results when a pending
reservation is absent. Channel-range helpers retain their first height for
zero-block input, and the graph syncer skips a nonexistent prefix when the
first queried block exceeds one reply chunk.
Verified with:
go test ./lnwallet ./lnwire ./discovery -count=1go test -race ./lnwallet -run '^TestHandleFundingCounterPartySigsMissingReservation -count=1go test -race ./discovery -run '^(TestGossipSyncerReplyChanRangeQueryBlockRange|TestGossipSyncerReplyChanRangeQueryDenseFirstBlock) -count=1