-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Include chain in client node name. #2548
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why don't we name wallets when we create them? (at random by default and otherwise using a user provided name)
Good idea, maybe that's more useful, and also more readable: In the tests they could simply be "Client 1" and "Client 2". |
@@ -161,7 +161,7 @@ async fn test_chain_listener() -> anyhow::Result<()> { | |||
delivery, | |||
false, | |||
[chain_id0], | |||
"Client node", | |||
format!("Client node for {:.8}", chain_id0), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is a minor point, but I find it a little odd that the Client
has a name
associated with its constructor. Though of course, this is not part of this PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Better logging is always welcomed.
Merging this, to make it easier to debug issues on |
Motivation
The
Client
is always called"Client node"
. This makes debugging difficult in tests involving multiple clients.Proposal
Include the chain ID(s) in the name.
Test Plan
No changed logic, but it should make debugging end-to-end tests easier.
Release Plan
Links