Skip to content
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

[Test] Add neg test for splice_channel with insufficient inputs #3674

Merged
merged 1 commit into from
Mar 24, 2025

Conversation

optout21
Copy link
Contributor

@optout21 optout21 commented Mar 18, 2025

In the splice_channel() API the user has to provide the intended splice-in contribution, as well as the inputs that are used to cover that. In case the inputs are not enough (to cover the intended contribution plus proportional fees), an error is returned.
This small PR adds a test for that.

@ldk-reviews-bot
Copy link

ldk-reviews-bot commented Mar 18, 2025

👋 Thanks for assigning @jkczyz as a reviewer!
I'll wait for their review and will help manage the review process.
Once they submit their review, I'll check if a second reviewer would be helpful.

@optout21 optout21 requested review from jkczyz and wpaulino March 18, 2025 09:44
@optout21 optout21 force-pushed the splice-init-neg-test branch from e44e0fb to 09520b4 Compare March 19, 2025 01:32
@optout21
Copy link
Contributor Author

Addressed review comments (jkczyz)

@optout21 optout21 requested a review from jkczyz March 19, 2025 01:35
jkczyz
jkczyz previously approved these changes Mar 19, 2025
@ldk-reviews-bot
Copy link

🔔 1st Reminder

Hey @wpaulino! This PR has been waiting for your review.
Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.

@ldk-reviews-bot
Copy link

🔔 2nd Reminder

Hey @wpaulino! This PR has been waiting for your review.
Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.

@ldk-reviews-bot
Copy link

🔔 3rd Reminder

Hey @wpaulino! This PR has been waiting for your review.
Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.

Copy link
Member

@shaavan shaavan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great to me! Just a few minor nits—let me know if they make sense. 🚀

@optout21
Copy link
Contributor Author

optout21 commented Mar 24, 2025

Incorporated minor suggestions from @shaavan . thx. Squashed into one commit, as changes were minimal.

Copy link

codecov bot commented Mar 24, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.20%. Comparing base (d671596) to head (a0fa32e).
Report is 8 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3674      +/-   ##
==========================================
- Coverage   89.26%   89.20%   -0.06%     
==========================================
  Files         155      155              
  Lines      119911   119954      +43     
  Branches   119911   119954      +43     
==========================================
- Hits       107038   107007      -31     
- Misses      10262    10327      +65     
- Partials     2611     2620       +9     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@wpaulino wpaulino merged commit 0721ba5 into lightningdevkit:main Mar 24, 2025
26 of 27 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants