Skip to content

Fix incorrect logging during RBF or rebroadcast #3482

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

Merged
merged 1 commit into from
Dec 12, 2024

Conversation

morehouse
Copy link
Contributor

We were incorrectly logging RBF'd transactions as not RBF'd and vice versa.

Copy link

codecov bot commented Dec 11, 2024

Codecov Report

Attention: Patch coverage is 75.00000% with 1 line in your changes missing coverage. Please review.

Project coverage is 89.69%. Comparing base (ddeaab6) to head (94ad5be).
Report is 16 commits behind head on main.

Files with missing lines Patch % Lines
lightning/src/chain/onchaintx.rs 75.00% 0 Missing and 1 partial ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3482      +/-   ##
==========================================
- Coverage   89.69%   89.69%   -0.01%     
==========================================
  Files         130      130              
  Lines      107472   107614     +142     
  Branches   107472   107614     +142     
==========================================
+ Hits        96396    96520     +124     
- Misses       8674     8691      +17     
- Partials     2402     2403       +1     

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

@@ -504,7 +504,7 @@ impl<ChannelSigner: EcdsaChannelSigner> OnchainTxHandler<ChannelSigner> {
.map(|(_, new_feerate, claim)| {
let mut bumped_feerate = false;
Copy link
Contributor

@arik-so arik-so Dec 11, 2024

Choose a reason for hiding this comment

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

thanks so much! Can we use this opportunity to also rename bumped_feerate to something like is_feerate_bumped or did_bump_feerate or feerate_was_bumped or really anything that doesn't make it sound as though it's the actual numeric value of the new fee rate?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done.

Copy link
Contributor

@vincenzopalazzo vincenzopalazzo left a comment

Choose a reason for hiding this comment

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

LGTM aside of the arik comment

@morehouse morehouse force-pushed the fix_rebroadcast_logging branch from a7f6a80 to 2620477 Compare December 12, 2024 08:48
We were incorrectly logging RBF'd transactions as not RBF'd and vice
versa.
@morehouse morehouse force-pushed the fix_rebroadcast_logging branch from 2620477 to 94ad5be Compare December 12, 2024 08:49
Copy link
Contributor

@tnull tnull left a comment

Choose a reason for hiding this comment

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

Thanks!

@tnull tnull merged commit 6f5f249 into lightningdevkit:main Dec 12, 2024
16 of 19 checks passed
@morehouse morehouse deleted the fix_rebroadcast_logging branch December 12, 2024 16:39
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.

4 participants