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

release: create branch for v0.18.5-beta.rc1 #9460

Merged
merged 41 commits into from
Jan 31, 2025
Merged

Conversation

guggero
Copy link
Collaborator

@guggero guggero commented Jan 30, 2025

JssDWt and others added 30 commits January 28, 2025 17:56
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)`.
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.
@guggero guggero added golang/build system Related to the go language and compiler releases no-changelog labels Jan 30, 2025
@guggero guggero added this to the v0.18.5 milestone Jan 30, 2025
@guggero guggero self-assigned this Jan 30, 2025
Copy link
Contributor

coderabbitai bot commented Jan 30, 2025

Important

Review skipped

Auto reviews are limited to specific labels.

🏷️ Labels to auto review (1)
  • llm-review

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


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?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

Pull reviewers stats

Stats of the last 30 days for lnd:

User Total reviews Time to review Total comments
guggero
🥇
8
▀▀
6h 3m
7
ellemouton
🥈
7
▀▀
3d 16h 19m
▀▀
8
ziggie1984
🥉
6
▀▀
7h 14m
18
▀▀▀
yyforyongyu
4
6h 31m
3
bhandras
2
45m
0
bitromortac
2
1d 25m
4
saubyk
2
13h 37m
1
alexbosworth
1
4h
1
Roasbeef
1
1d 8h 55m
7
morehouse
1
2d 2h 14m
2
GeorgeTsagk
1
2d 8h 44m
6
Abdulkbk
1
2d 21h 10m
0
GustavoStingelin
1
8d 17h 37m
▀▀▀▀
1

@guggero
Copy link
Collaborator Author

guggero commented Jan 30, 2025

Unit test failures are due to a mismatch in the fuzz corpora. We pull the files for master but this release branch doesn't have the latest corresponding changes in the fuzz tests.
And the integration test failures are due to found active channels, please close them properly, so a cleanup issue which can be ignored as well.

@starius
Copy link
Collaborator

starius commented Jan 30, 2025

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 (--utxo flag) added recently.

@starius
Copy link
Collaborator

starius commented Jan 30, 2025

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.

sputn1ck and others added 2 commits January 30, 2025 16:40
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.
@guggero
Copy link
Collaborator Author

guggero commented Jan 30, 2025

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.
@guggero
Copy link
Collaborator Author

guggero commented Jan 30, 2025

Added #9462.

@guggero guggero requested a review from Roasbeef January 30, 2025 16:28
@guggero
Copy link
Collaborator Author

guggero commented Jan 30, 2025

Added #9411 to get itests working.

Copy link
Member

@Roasbeef Roasbeef left a 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

Copy link
Member

Choose a reason for hiding this comment

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

@Roasbeef Roasbeef merged commit 288f0e1 into 0-18-5-branch Jan 31, 2025
24 of 27 checks passed
@guggero guggero deleted the 0-18-5-branch-rc1 branch January 31, 2025 20:16
@ziggie1984
Copy link
Collaborator

For RC2 we should also include: #9383

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
golang/build system Related to the go language and compiler no-changelog releases
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants