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

wasp-cli metrics nodeconn output only zeroes? #3416

Open
TeeVeeEss opened this issue May 26, 2024 · 0 comments
Open

wasp-cli metrics nodeconn output only zeroes? #3416

TeeVeeEss opened this issue May 26, 2024 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@TeeVeeEss
Copy link

Describe the bug
Command is not showing any information.

To Reproduce

  1. Download the latest wasp-cli, unzip and navigate to that folder
  2. Use this command ./wasp-cli metrics nodeconn
  3. Output is only showing zeroes:
Password required to open/create secured storage.
Password:
Following chains are registered for L1 events:
        smr1prxvwqvwf7nru5q5xvh5thwg54zsm2y4wfnk6yk56hj3exxkg92mx20wl3s
------------                         -----  ---------                      ------------
Message name                         Total  Last time                      Last message
------------                         -----  ---------                      ------------
Milestone                       IN   0      0001-01-01 00:00:00 +0000 UTC
State output                    IN   0      0001-01-01 00:00:00 +0000 UTC
Alias output                    IN   0      0001-01-01 00:00:00 +0000 UTC
Output                          IN   0      0001-01-01 00:00:00 +0000 UTC
On ledger request               IN   0      0001-01-01 00:00:00 +0000 UTC
Tx inclusion state              IN   0      0001-01-01 00:00:00 +0000 UTC
Publish state transaction       OUT  0      0001-01-01 00:00:00 +0000 UTC
Publish governance transaction  OUT  0      0001-01-01 00:00:00 +0000 UTC
Pull latest output              OUT  0      0001-01-01 00:00:00 +0000 UTC
Pull tx inclusion state         OUT  0      0001-01-01 00:00:00 +0000 UTC  0x0000000000000000000000000000000000000000000000000000000000000000
Pull output by ID               OUT  0      0001-01-01 00:00:00 +0000 UTC  0x00000000000000000000000000000000000000000000000000000000000000000000

Expected behavior
Some decent info or an explanation why it's all zeroes.

Network and versioning

  • Type of L1 network: Shimmer
  • Type of Wasp chain: ShimmerEVM
  • Interaction method: Wasp-cli
  • Interaction software: wasp-cli
  • Version of Wasp: wasp 1.2.0-alpha.1, wasp-cli_1.2.0-alpha.1_Linux_x86_64
  • My wasp node has pubkey 0xb1f4bb0c3938963eaa9216d60693cd4b1bcdc862c35b30dec94c0342b54b4d69 and is peering with wasp-public-3.h.shimmer.shimmer.network and wasp-public-2.h.shimmer.shimmer.network
@TeeVeeEss TeeVeeEss added the bug Something isn't working label May 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants