-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
release: create branch for v0.18.5-beta.rc1 #9460
Conversation
If a node contains a channel, but doesn't have a corresponding edge in the graph database, updating the channel policy would fail. In this commit the edge is recreated if the channel exists. This ensures a node can recover from a missing edge in the graph database by calling updatechanpolicy.
This is a robustness option to ensure LND doesn't crash when this function is accidentally called with `AddChannelEdge(edge, nil)`.
This reverts commit 67419a7.
To make this itest work reliably with multiple parallel SQL transactions, we need to count both the settle and final HTLC events. Otherwise, sometimes the final events from earlier forwards are counted before the forward events from later forwards, causing a miscount of the settle events. If we expect both the settle and final event for each forward, we don't miscount.
We make sure that HTLCs which have already been decided upon are resolved before before allowing the external interceptor to potentially cancel them back. This makes the implementation for the external HTLC interceptor more streamlined.
We introduce a new specific fail resolution error when the external HTLC interceptor denies the incoming HTLC. Moreover we introduce a new traffic shaper method which moves the implementation of asset HTLC to the external layers. Moreover itests are adopted to reflect this new change.
The invoiceregistry test suite also includes unit tests for multi part payment especially also including payments to AMP invoices.
We always fetch the HTLCs for the specific setID, so there is no need to keep this code. In earlier versions we would call the UpdateInvoice method with `nil` for the setID therefore we had to lookup the AMPState. However this was error prune because in case one partial payment times-out the AMPState would change to cancelled and that could lead to not resolve HTLCs.
We need to make sure if we cancel an AMP invoice we also cancel all remaining HTLCs back.
Important Review skippedAuto reviews are limited to specific labels. 🏷️ Labels to auto review (1)
Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the 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 using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Pull reviewers statsStats of the last 30 days for lnd:
|
Unit test failures are due to a mismatch in the fuzz corpora. We pull the files for |
Is #9226 a good candidate to be included into this release? It is a small lncli only patch, fixing miscalculation of the amount to be sent. Got into it several times after started using coin selection ( |
I propose to update Go used to build this release to the latest bugfix release (Go 1.22.11). Currently Go 1.22.6 is used. |
This commit fixes the display of the amount when selecting utxos for the sendcoins command and combining it with the `-sweepall` flag. Prior this would show the full balance of the wallet. Now it shows the total amount of the selected utxos.
Added #9226. |
This commit fixes a couple of issues that only occur on the branch we use for minor releases. The branch doesn't contain all refactors and cleanups so a couple of very minor things need to be fixed. Because we don't have all new features of the master branch we also can't apply the fuzz corpora for the master branch as that can lead to false positives.
Added #9462. |
Added #9411 to get itests working. |
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 🐋
- [Tooling and Documentation](#tooling-and-documentation) | ||
|
||
# Bug Fixes | ||
|
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.
Missing a release notes entry here: https://github.com/lightningnetwork/lnd/pull/9459/files#diff-7729387e95c78c2453c35bb8cf6dfe9afe197e34d0966f9fa07033ce22f9985aR22-R24
For RC2 we should also include: #9383 |
Preparation PR to kick off the
v0.18.5-beta.rc1
release.This PR includes rebased versions of the following PRs (in order):