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

itest: universe server harness uses a dedicated LND node #800

Merged
merged 1 commit into from
Feb 14, 2024

Conversation

ffranr
Copy link
Contributor

@ffranr ffranr commented Feb 14, 2024

In this commit we ensure that the universe server harness uses a new dedicated LND node. The universe harness previously used the Bob standby LND node. This change allows us to use an in-test tapd node with LND node Bob without conflicting with the universe server tapd node.

This change will be important when passing messages between tapd nodes (e.g. RFQ system) via LND nodes.

This work is necessary to complete: #766

In this commit we ensure that the universe server harness uses a new
dedicated LND node. The universe harness previously used the Bob standby
LND node. This change allows us to use an in-test tapd node with LND
node Bob without conflicting with the universe server tapd node.

This change will be important when passing messages between tapd nodes
(e.g. RFQ system) via LND nodes.
@ffranr ffranr self-assigned this Feb 14, 2024
Copy link
Member

@guggero guggero left a comment

Choose a reason for hiding this comment

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

LGTM 🎉

I think it makes sense to use a specific node for the universe.
But I'd still say that for a test where we require a small test network of three nodes it would make sense to spin up three extra lnds, just to make sure we don't "pollute" the long-running nodes with channel state (which might have an impact on other tests).

Copy link
Member

@GeorgeTsagk GeorgeTsagk left a comment

Choose a reason for hiding this comment

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

LGTM

Just to make sure, this new harness node is introduced here in order to be used in future itests that require it to be a separate node? Are we going to also update all existing itests to use the uniServerLndHarness instead of Bob?

Edit: this seems to be part of the setup code, so effectively it affects current itest too I suppose

@ffranr ffranr added this pull request to the merge queue Feb 14, 2024
Merged via the queue into main with commit 783b7b3 Feb 14, 2024
14 checks passed
@guggero guggero deleted the itest-uni-server-lnd-node branch February 14, 2024 14:13
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.

3 participants