Skip to content

Refactor Payment PR 3#9844

Merged
yyforyongyu merged 7 commits intolightningnetwork:masterfrom
ziggie1984:refactor-payments-code-03
Aug 13, 2025
Merged

Refactor Payment PR 3#9844
yyforyongyu merged 7 commits intolightningnetwork:masterfrom
ziggie1984:refactor-payments-code-03

Conversation

@ziggie1984
Copy link
Collaborator

@ziggie1984 ziggie1984 commented May 20, 2025

This Refactor commit starts moving payment related code into its own package.
It still keeps the KVPaymentDB implementation in the channeldb package. This will be moved to the payments package in the next PR.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented May 20, 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.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @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.

@ziggie1984 ziggie1984 self-assigned this May 20, 2025
@ziggie1984 ziggie1984 added payments Related to invoices/payments refactoring no-changelog labels May 20, 2025
@ziggie1984 ziggie1984 added this to the v0.20.0 milestone May 20, 2025
@ziggie1984 ziggie1984 marked this pull request as ready for review May 20, 2025 19:07
@ziggie1984 ziggie1984 force-pushed the refactor-payments-code-03 branch from 50f580b to 90108ed Compare May 20, 2025 19:12
@ziggie1984 ziggie1984 force-pushed the refactor-payments-code-03 branch 3 times, most recently from 8658c85 to b308ed0 Compare May 21, 2025 07:17
@ziggie1984 ziggie1984 moved this to In progress in lnd v0.20 May 21, 2025
@ziggie1984 ziggie1984 force-pushed the refactor-payments-code-03 branch from b308ed0 to 3a573e0 Compare May 21, 2025 07:51
@ziggie1984 ziggie1984 force-pushed the refactor-payments-code-03 branch from 3a573e0 to 7faf0b0 Compare August 7, 2025 16:45
@ziggie1984 ziggie1984 force-pushed the refactor-payments-code-03 branch 2 times, most recently from 8c5b919 to 4b08ee1 Compare August 7, 2025 17:46
Copy link
Collaborator

@ellemouton ellemouton left a comment

Choose a reason for hiding this comment

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

Nice! some nits

"github.com/lightningnetwork/lnd/lntypes"
"github.com/lightningnetwork/lnd/lnutils"
"github.com/lightningnetwork/lnd/lnwire"
paymentsdb "github.com/lightningnetwork/lnd/payments/db"
Copy link
Member

Choose a reason for hiding this comment

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

nit: consider name it pdb for brevity?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

currently I prefer the longer name, but happy to change it in PR4, so that I don't end up in rebase hell. (most of the refactor PRs are ready so I would need to rebase everything all the time, so going to rename it after the last refactor for the whole series.

@yyforyongyu
Copy link
Member

/gemini review

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request is a significant refactoring that moves payment-related code from the channeldb package to a new, dedicated payments/db package. This is a great architectural improvement that enhances modularity and separation of concerns. The changes are extensive but appear to be consistently applied across the codebase. The introduction of a paymentsdb package with its own options and error types is a solid step forward. My review focuses on ensuring adherence to the project's style guide, particularly regarding line length, which I've found a few violations of.

@ziggie1984 ziggie1984 force-pushed the refactor-payments-code-03 branch 2 times, most recently from 99ed9d0 to bbc8e63 Compare August 11, 2025 14:11
@ziggie1984 ziggie1984 force-pushed the refactor-payments-code-03 branch from bbc8e63 to c010c72 Compare August 11, 2025 14:14
@ziggie1984 ziggie1984 requested a review from yyforyongyu August 11, 2025 14:18
@ziggie1984 ziggie1984 force-pushed the refactor-payments-code-03 branch from 47dca79 to b51e82b Compare August 11, 2025 14:36
We add a context for the query method because the query method
is part of the paymentDB interface and for the SQL case
we will need the context for this method because the native
SQL drivers demand one. So we add it for the kv implementation
here as well so we can then make use of the new interface type.
We introduce a new package paymentsDB and start by moving the
payment specifc errors from the channeldb package to the
paymentsDB package. We also fix linter issues which showed up
due to changing this code part.
Instead of the ChannelState struct we now use the kv backend
interface for the payment kv database.
@ziggie1984 ziggie1984 force-pushed the refactor-payments-code-03 branch from b51e82b to 4e0af2f Compare August 11, 2025 14:44
@ziggie1984 ziggie1984 moved this from In progress to In review in lnd v0.20 Aug 12, 2025
Copy link
Member

@yyforyongyu yyforyongyu left a comment

Choose a reason for hiding this comment

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

🦾

// db is the underlying database implementation.
db kvdb.Backend

keepFailedPaymentAttempts bool
Copy link
Member

Choose a reason for hiding this comment

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

We should keep the docs.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

added in PR4

}, nil
}

var paymentsTopLevelBuckets = [][]byte{
Copy link
Member

Choose a reason for hiding this comment

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

would be nice to add more docs, can do it in a later pr tho.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

added in PR4

@yyforyongyu yyforyongyu merged commit c6a9116 into lightningnetwork:master Aug 13, 2025
36 of 39 checks passed
@github-project-automation github-project-automation bot moved this from In review to Done in lnd v0.20 Aug 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no-changelog payments Related to invoices/payments refactoring

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants