-
Notifications
You must be signed in to change notification settings - Fork 342
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle fallible per commitment point in channel establishment #3109
Open
alecchendev
wants to merge
22
commits into
lightningdevkit:main
Choose a base branch
from
alecchendev:2024-06-async-commit-point-funding
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 1 commit
Commits
Show all changes
22 commits
Select commit
Hold shift + click to select a range
f49df83
Async signing test util follow ups
alecchendev cbb4a9e
Move clearing signer funding signed flag to signer_unblocked
alecchendev 3f840f2
Move clearing signer commitment flag to signer_unblocked
alecchendev df10ff4
Clear signer pending funding created flag
alecchendev 3e1cae5
Add logger as parameter in creating ChannelContext
alecchendev cb9ba76
Add HolderCommitmentPoint::Uninitialized
alecchendev 6013f0d
f - improve holder commitment docs
alecchendev 3d2f215
f - fix debug assertion
alecchendev 0c130d9
Split HolderCommitmentPoint::advance off into separate function
alecchendev 4494d96
Return an error if we fail to advance our commitment number
alecchendev 3c82bb5
Change get_per_commitment_point to return result type
alecchendev a4eb312
Handle fallible commitment point when getting open_channel message
alecchendev 1a76f82
Handle sending open_channel when signer is unblocked
alecchendev 41e4139
f - try_resolve_pending
alecchendev 1e9a36f
Handle fallible commitment point when getting accept_channel
alecchendev 84f4ff3
Handle sending accept_channel when signer is unblocked
alecchendev 02b9f00
f - try_resolve_pending
alecchendev 7bf5c62
Handle fallible commitment point when getting channel_ready
alecchendev ccbe92d
Handle sending channel_ready when commitment point is unblocked
alecchendev db9f2e6
f - try_resolve_pending
alecchendev 68f1d8a
Add test for async open and accept channel
alecchendev b798ffa
f - test unblocking signer ops in different orders for various tests
alecchendev File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought we were going to first handle all the async cases post-funding and then add support for handling the async case during initial channel bring up in a separate PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sorry for the delay, yea you're right, i just forgot! will be back to prioritizing this next week