-
Notifications
You must be signed in to change notification settings - Fork 407
export send_onion_message_using_path for testing #2868
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
export send_onion_message_using_path for testing #2868
Conversation
WalkthroughThe update involves modifying the accessibility of the Changes
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
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.
Review Status
Actionable comments generated: 0
Configuration used: CodeRabbit UI
Files selected for processing (1)
- lightning/src/onion_message/messenger.rs (1 hunks)
Additional comments: 1
lightning/src/onion_message/messenger.rs (1)
- 810-811: The visibility change of
send_onion_message_using_path
to public under the_test_utils
feature flag is correctly implemented. This change facilitates testing by allowing direct access to this function when the feature flag is enabled, without affecting the standard execution context.
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## main #2868 +/- ##
==========================================
+ Coverage 88.54% 90.41% +1.86%
==========================================
Files 115 116 +1
Lines 92277 101841 +9564
Branches 92277 101841 +9564
==========================================
+ Hits 81706 92076 +10370
+ Misses 8068 7334 -734
+ Partials 2503 2431 -72 ☔ View full report in Codecov by Sentry. |
We upgrade to LDK v120 because we need the new blinded route features within. On top of that we add the changes in a small PR we submitted, which we need in order to send an onion message across along a specified path for LNDK's integration tests: lightningdevkit/rust-lightning#2868
We update to ldk v20 for the latest blinded route updates, namely being able to create a blinded route that's more than one hop. On top of that we use a custom versoin with a small change, which we need in order to send an onion message along a specified path for LNDK's integration tests: lightningdevkit/rust-lightning#2868
We update to ldk v20 for the latest blinded route updates, namely being able to create a blinded route that's more than one hop. On top of that we use a custom versoin with a small change, which we need in order to send an onion message along a specified path for LNDK's integration tests: lightningdevkit/rust-lightning#2868
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.
This was the previous public interface, which we still use in testing, too.
We update to ldk v20 for the latest blinded route updates, namely being able to create a blinded route that's more than one hop. On top of that we use a custom versoin with a small change, which we need in order to send an onion message along a specified path for LNDK's integration tests: lightningdevkit/rust-lightning#2868
We update to ldk v20 for the latest blinded route updates, namely being able to create a blinded route that's more than one hop. On top of that we use a custom versoin with a small change, which we need in order to send an onion message along a specified path for LNDK's integration tests: lightningdevkit/rust-lightning#2868
We upgrade to LDK v120 because we need the new blinded route features within. On top of that we add the changes in a small PR we submitted, which we need in order to send an onion message across along a specified path for LNDK's integration tests: lightningdevkit/rust-lightning#2868
We update to ldk v20 for the latest blinded route updates, namely being able to create a blinded route that's more than one hop. On top of that we use a custom versoin with a small change, which we need in order to send an onion message along a specified path for LNDK's integration tests: lightningdevkit/rust-lightning#2868
We update to ldk v20 for the latest blinded route updates, namely being able to create a blinded route that's more than one hop. On top of that we use a custom versoin with a small change, which we need in order to send an onion message along a specified path for LNDK's integration tests: lightningdevkit/rust-lightning#2868
We update to ldk v20 for the latest blinded route updates, namely being able to create a blinded route that's more than one hop. On top of that we use a custom versoin with a small change, which we need in order to send an onion message along a specified path for LNDK's integration tests: lightningdevkit/rust-lightning#2868
We update to ldk v20 for the latest blinded route updates, namely being able to create a blinded route that's more than one hop. On top of that we use a custom versoin with a small change, which we need in order to send an onion message along a specified path for LNDK's integration tests: lightningdevkit/rust-lightning#2868
We update to ldk v20 for the latest blinded route updates, namely being able to create a blinded route that's more than one hop. On top of that we use a custom versoin with a small change, which we need in order to send an onion message along a specified path for LNDK's integration tests: lightningdevkit/rust-lightning#2868
We update to ldk v20 for the latest blinded route updates, namely being able to create a blinded route that's more than one hop. On top of that we use a custom versoin with a small change, which we need in order to send an onion message along a specified path for LNDK's integration tests: lightningdevkit/rust-lightning#2868
We update to ldk v20 for the latest blinded route updates, namely being able to create a blinded route that's more than one hop. On top of that we use a custom versoin with a small change, which we need in order to send an onion message along a specified path for LNDK's integration tests: lightningdevkit/rust-lightning#2868
We update to ldk v20 for the latest blinded route updates, namely being able to create a blinded route that's more than one hop. On top of that we use a custom versoin with a small change, which we need in order to send an onion message along a specified path for LNDK's integration tests: lightningdevkit/rust-lightning#2868
This is a small PR to export OnionMessenger's send_onion_message_using_path for testing. It can be turned on when the "_test_utils" feature is set. Context: We'd like to use this function in LNDK's tests and @jkczyz suggested this approach.