Skip to content

kwil-cli logs unexpected info #1238

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

Closed
brennanjl opened this issue Jan 17, 2025 · 2 comments
Closed

kwil-cli logs unexpected info #1238

brennanjl opened this issue Jan 17, 2025 · 2 comments
Assignees

Comments

@brennanjl
Copy link
Collaborator

$ kwil-cli utils ping
time="2025-01-16 21:49:52.235" level=WARN msg="node reports that it is not healthy: &{{kwil-test-chain 15 6ae14d0025fd6900480746d27bc5d403b86c8e3d52e75cc1fe925088bc71a1ac} true 0.2.0 -62135596800000 9223372036854 false 15 03d13507df1028696e24158c2808bea9e9dd8f2c1a54dee0edf95d1c65f8cb86 0 open}"
time="2025-01-16 21:49:52.235" level=WARN msg="chain ID not set, trusting chain ID from remote host!" chainID=kwil-test-chain
pong
@brennanjl brennanjl self-assigned this Jan 17, 2025
@jchappelow
Copy link
Collaborator

This is also an issue with the RPC client and the RPC server's health check. Will look at it from that angle, but there's probably a default logger instance created by kwil-cli for the RPC client where there shouldn't be one.

@brennanjl
Copy link
Collaborator Author

This is also an issue with the RPC client and the RPC server's health check. Will look at it from that angle, but there's probably a default logger instance created by kwil-cli for the RPC client where there shouldn't be one.

That was exactly what was going on

Resolved in #1260

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

No branches or pull requests

2 participants