Skip to content

[5/7]: multi: thread ChannelUpdate through codebase #8254

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

Draft
wants to merge 15 commits into
base: elle-g175-thread-interfaces-2
Choose a base branch
from

Conversation

ellemouton
Copy link
Collaborator

This is part of the Gossip 1.75 epic.

Depends on #8252 so only the last 14 commits are new

In this PR, we continue threading the new interfaces throughout the code base.
All that is done here is the threading of the new lnwire.ChannelUpdate interface through
the code base. It is split into multiple commits for easier review.

@ellemouton ellemouton marked this pull request as draft December 6, 2023 13:41
@ellemouton ellemouton mentioned this pull request Dec 6, 2023
21 tasks
@ellemouton ellemouton force-pushed the g175-thread-chan-update branch from c76c05b to 96afa6e Compare January 11, 2024 15:28
@ellemouton ellemouton changed the base branch from master to elle-g175-thread-interfaces-2 January 11, 2024 15:29
@ellemouton ellemouton force-pushed the elle-g175-thread-interfaces-2 branch from 74e232b to 71e245c Compare February 12, 2024 13:28
@ellemouton ellemouton force-pushed the g175-thread-chan-update branch from 96afa6e to 5c11c93 Compare February 12, 2024 13:30
Copy link
Contributor

coderabbitai bot commented Feb 12, 2024

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>.
    • 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.
    • @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 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.

@ellemouton ellemouton force-pushed the g175-thread-chan-update branch from 5c11c93 to e1b873e Compare September 3, 2024 11:15
@ellemouton ellemouton force-pushed the elle-g175-thread-interfaces-2 branch from 71e245c to 183d184 Compare September 3, 2024 11:17
// SignMessageSchnorr signs the given message, single or double SHA256
// hashing it first, with the private key described in the key locator
// and the optional Taproot tweak applied to the private key.
SignMessageSchnorr(keyLoc KeyLocator, msg []byte, doubleHash bool,
Copy link
Member

Choose a reason for hiding this comment

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

This is the SingleKeyMessageSigner (bound to a single pubkey), why does it need to accept a KeyLocator? I think you instead want MessageSignerRing if you wnat to be able to pass in ahother keyloc.

@@ -337,8 +336,7 @@ type Config struct {

// SignAliasUpdate is used to re-sign a channel update using the
// remote's alias if the option-scid-alias feature bit was negotiated.
SignAliasUpdate func(u *lnwire.ChannelUpdate1) (*ecdsa.Signature,
error)
SignAliasUpdate func(u lnwire.ChannelUpdate) error
Copy link
Member

Choose a reason for hiding this comment

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

Should update the godoc, as IIUC now the sig will only be set in place instead of also being returned.

@@ -221,8 +220,7 @@ type Config struct {
// option_scid_alias channels. This avoids a potential privacy leak by
// replacing the public, confirmed SCID with the alias in the
// ChannelUpdate.
SignAliasUpdate func(u *lnwire.ChannelUpdate1) (*ecdsa.Signature,
error)
SignAliasUpdate func(u lnwire.ChannelUpdate) error
Copy link
Member

Choose a reason for hiding this comment

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

Same here re godoc.

case *models.ChannelEdgePolicy1:
return !timestamp.After(edge.LastUpdate)
default:
panic(fmt.Sprintf("unhandled: %T", edges[1]))
Copy link
Member

Choose a reason for hiding this comment

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

What about the chan upd2 case?

response.Code = lnrpc.Failure_EXPIRY_TOO_SOON
response.ChannelUpdate = marshallChannelUpdate(&onionErr.Update)
response.ChannelUpdate = update1
response.ChannelUpdate_2 = update2
Copy link
Member

Choose a reason for hiding this comment

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

See comment on prior PR, I think we can just merge the two protos, and add a type field. This way clients will just work if they're wanting to consume updates over the streaming RPC.

flags lnwire.ChanUpdateChanFlags
disabled bool

direction bool
Copy link
Member

Choose a reason for hiding this comment

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

Missing godoc comment.

}

oldTimestamp := uint32(0)
var (
older = false
Copy link
Member

Choose a reason for hiding this comment

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

👍

height := upd.BlockHeight

edge1Height, edge2Height, exists, isZombie, err :=
b.cfg.Graph.HasChannelEdge2(chanID.ToUint64())
Copy link
Member

Choose a reason for hiding this comment

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

I think if we can come up with an abstraction over the return values here (height vs timestamp), then we can condense this function a bit and eliminate some of the duplication.

@@ -3848,6 +3876,39 @@ func (d *AuthenticatedGossiper) ShouldDisconnect(pubkey *btcec.PublicKey) (
return false, nil
}

func (d *AuthenticatedGossiper) updateWithinRebroadcastInterval(
Copy link
Member

Choose a reason for hiding this comment

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

Missing godoc comment.

@saubyk saubyk added this to the 0.20.0 milestone Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants