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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

channeldb: add persist nodeannounment config in db #8690

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

Abdulkbk
Copy link

@Abdulkbk Abdulkbk commented Apr 25, 2024

In this commit, we save the node announcement config in the database so that we can retrieve the config later and use it when a node restarts.

closes #7123

Change Description

Description of change / link to associated issue.
We start by checking the configuration from the configuration file lnd.conf or arguments when the node starts. If the configuration is absent, we check for the ones persisted on disk and use them; otherwise, we resolve to the default settings.

Steps to Test

Steps for reviewers to follow to test the change.

  • Make sure no alias is not set in your lnd.conf
  • Use the updatenodeannouncement RPC call and set something as your alias
  • Verify the alias is set using lncli getinfo
  • Now stop and start the node again and run lncli getinfo again
  • You'll see that the alias is set to the first 10 characters of the node's pubkey

Pull Request Checklist

Testing

  • Your PR passes all CI checks.
  • Tests covering the positive and negative (error paths) are included.
  • Bug fixes contain tests triggering the bug to prevent regressions.

Code Style and Documentation

馃摑 Please see our Contribution Guidelines for further guidance.

In this commit, we save nodeannouncement config in the database
so that we will be able to retrieve the config later and use them
on retart

Signed-off-by: Abdullahi Yunus <abdoollahikbk@gmail.com>
Copy link

coderabbitai bot commented Apr 25, 2024

Important

Review Skipped

Auto reviews are disabled on this repository.

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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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.

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 as 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 full the review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

In this commit, we check for nodeannouncement alias in the db before
creating a disk representation of a node. If there none, we default to
first 10 characters of our pubkey.
@Abdulkbk Abdulkbk marked this pull request as ready for review May 12, 2024 06:59
In this commit, we check for alias that are persisted in disk and use
them when the node is restarting.
Copy link
Contributor

@Chinwendu20 Chinwendu20 left a comment

Choose a reason for hiding this comment

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

Nice work, Left questions and doubts about the architecture

channeldb/db.go Show resolved Hide resolved
Copy link
Contributor

Choose a reason for hiding this comment

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

I am not sure this should be channeldb as it seems to not correlate with what is done here, perhaps a separate db?
@guggero @ellemouton what do you think?

Copy link
Collaborator

Choose a reason for hiding this comment

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

channeldb does store everything about other channel node announcements today.

Copy link
Contributor

Choose a reason for hiding this comment

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

ohh could not find where node announcements were persisted in the code. Just saw that announcements were received and used to create lightningNode objects which were persisted in the graph database but just saw that even the graph database is created by channeldb

In that case maybe we can use the miscDB seems in line in name for this functionality or create another field for it in the server struct instead of making it a part of the channelStateDB

Want to learn from what you think

Copy link
Author

@Abdulkbk Abdulkbk May 31, 2024

Choose a reason for hiding this comment

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

ohh could not find where node announcements were persisted in the code. Just saw that announcements were received and used to create lightningNode objects which were persisted in the graph database but just saw that even the graph database is created by channeldb

In that case maybe we can use the miscDB seems in line in name for this functionality or create another field for it in the server struct instead of making it a part of the channelStateDB

Want to learn from what you think

Using the miscDB seems like a good idea since it contains all the other databases within channel db. I used it here in fact to load the persisted config.

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.

Thanks for the PR,
I think we want things to be more general and not just for the alias. Ie, for any of the fields you can change via UpdateNodeAnnouncement

Copy link
Collaborator

Choose a reason for hiding this comment

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

channeldb does store everything about other channel node announcements today.

type NodeAnnouncementDB struct {
backend kvdb.Backend
}

Copy link
Collaborator

Choose a reason for hiding this comment

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

we already persist our node announcement in the bucket storing all the collected node announcement. Can we not just grab our latest one from there?

@Abdulkbk
Copy link
Author

Nice work, Left questions and doubts about the architecture

Thanks for reviewing @Chinwendu20. I will look at the comments, answer your questions, and address any suggestions you gave me

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.

[feature]: Allow persisting dynamic configured alias when not set in lnd.conf or arguments
3 participants