-
Notifications
You must be signed in to change notification settings - Fork 385
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
[Splicing] Partial, handle splice_init & splice_ack messages #3407
Conversation
3a3ff71
to
b85a9d7
Compare
6ac5f01
to
e274887
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3407 +/- ##
==========================================
+ Coverage 89.19% 89.25% +0.05%
==========================================
Files 152 152
Lines 118830 118841 +11
Branches 118830 118841 +11
==========================================
+ Hits 105993 106066 +73
+ Misses 10252 10201 -51
+ Partials 2585 2574 -11 ☔ View full report in Codecov by Sentry. |
19f8ab8
to
4ee3735
Compare
fd61390
to
6ee1aee
Compare
I have reorganized code, moved most single-channel checks and handling logic into |
bb3b4de
to
8e5e331
Compare
9bbdf58
to
b1ba24b
Compare
Rebased (post #3137) and squashed |
fb4968c
to
9ffe4b1
Compare
Rebased and squashed |
Review comments from @wpaulino addressed. |
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.
Mostly minor comments and nits, but note that one introduced test is broken.
9e9045c
to
b7c2d45
Compare
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.
LGTM. @wpaulino Good to squash the fixups?
Squashed into a single commit, prepared for merging. |
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.
Still waiting on CI to start... :(
Somehow CI got mixed up, showing failures for earlier commit... I'm not sure how to re-trigger. Commit ID is different. I know the issue being reported (conflict caused by #3016) but fixed previously. |
Did a commit amend & force push, let's see CI's response... |
For some reason (which I don't understand), when in the CI this PR branch is merged onto current main, a bunch of previous rebase merges get reverted, and compilation fails. Even though the PR branch was rebased to recent and has no conflicts. I have recreated the commit completely anew, hopefully this helps. |
Github shows that your branch is 33 commits behind. If I rebase your PR on upstream |
Handle the initial splice negotiation, without continuing to transaction negotiation: - `splice_channel()` for initiating splicing - handling of `splice_init` and `splice_ack` messages, with checks - `splice_ack` always fails (use case still imcomplete) - A test to go through the use case (`test_v1_splice_in`)
Rebased and fixed the compilation error locally. CI running now. |
Handle
splice_init
&splice_ack
messages, without performing splicing.splice_init
does not error, butsplice_ack
returns an error (and neither side continues with splicing).One next piece for splicing #3298 .
This can come before #3137 .