Skip to content

Conversation

@okekefrancis112
Copy link
Contributor

@okekefrancis112 okekefrancis112 commented Feb 8, 2026

  • Added a new test legacy_closed_channel_update_id_upgrade that verifies the upgrade path for nodes carrying legacy u64::MAX update IDs from pre-0.1 LDK.

Closes: #4104

@ldk-reviews-bot
Copy link

ldk-reviews-bot commented Feb 8, 2026

👋 I see @valentinewallace was un-assigned.
If you'd like another reviewer assignment, please click here.

@codecov
Copy link

codecov bot commented Feb 8, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.04%. Comparing base (2424c4a) to head (cff6161).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4397      +/-   ##
==========================================
+ Coverage   86.03%   86.04%   +0.01%     
==========================================
  Files         156      156              
  Lines      103092   103178      +86     
  Branches   103092   103178      +86     
==========================================
+ Hits        88694    88779      +85     
- Misses      11885    11888       +3     
+ Partials     2513     2511       -2     
Flag Coverage Δ
tests 86.04% <100.00%> (+0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ 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.

Copy link
Collaborator

@TheBlueMatt TheBlueMatt left a comment

Choose a reason for hiding this comment

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

Because review bandwidth is rather limited, please don't open a flood of PRs at once - give each new PR some time to get review cycles before you open up new ones. If you're looking for ways to contribute, try reviewing existing open PRs! Learning the codebase through review is likely to be way more fruitful than just writing code.

.is_err());
}

// Test that a monitor with a legacy u64::MAX update_id (from pre-0.1 LDK) can still be read
Copy link
Collaborator

Choose a reason for hiding this comment

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

By "upgrade test", the issue meant adding a test in the lightning-tests crate which actually uses an old version of LDK to get us into a state where we have to handle u64::MAX updates.

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.

Add Upgrade test for MonitorUpdatingPersister LEGACY_CLOSED_CHANNEL_UPDATE_ID writes

3 participants