panic: runtime error: index out of range [0] with length 0 about cosmos-exporter HOT 9 CLOSED

I still need to fix the error if no metadatas, panic isn't a nice solution here and is the opposite of intuitive. I'll fix the error message and then close it.

from cosmos-exporter.

Hi, can you run <app binary> query bank denom-metadata and post the output?
I'm assuming it returns the denoms information in a different way than any other binaries I've tested it on, but I don't have a Rizon fullnode unfortunately so I can't check it by myself.

from cosmos-exporter.

starsd query --node "tcp://127.0.0.11:26657" bank denom-metadata
metadatas: []
pagination:
  next_key: null
  total: "0"

I've checked also "stargaze" node and received the same info...

from cosmos-exporter.

Ummmm lol, it doesn't return any of the denom information and crashes about that. For example, here's what the command does on Sentinel:

sentinelhub query bank denom-metadata --node https://rpc.sentinel.co:443
metadatas:
- base: udvpn
  denom_units:
  - aliases: []
    denom: dvpn
    exponent: 6
  - aliases:
    - millidvpn
    denom: mdvpn
    exponent: 3
  - aliases:
    - microdvpn
    denom: udvpn
    exponent: 0
  description: The native staking token of the Sentinel Hub.
  display: dvpn
pagination:
  next_key: null
  total: "1"

as you can see, the metadatas is not empty.

You can fix it by running it by specifying --denom and --denom-coefficient manually, so it won't use the results from the node (something like --denom atolo --denom-coefficient 1000000), meanwhile the app should crash if no metatatas, but giving some fancy error in return. I'll fix it and close it after.

Let me know if the approach above would work for you.

from cosmos-exporter.

ok, thanks, I will check
for info - how it looks like balances output with denom here:
`rizond query --node "tcp://127.0.0.11:26657" bank balances rizon99999999999999999999999999999
balances:

• amount: "999"
  denom: uatolo
  pagination:
  next_key: null
  total: "0"
  `

from cosmos-exporter.

Yes, with "--denom-coefficient" it started without errors
Thanks again!
You can close issue.

from cosmos-exporter.

@sparkuss okay so I've published 0.2.1 which should've fixed it. Can you try reproducing the panic behaviour on the newer release? If it'll log the error and exit instead of panic this would be expected.

from cosmos-exporter.

@freak12techno yes, much better and understandable now:
11:59AM INF Got network status from Tendermint network=titan-1
11:59AM FTL No denom infos. Try running the binary with --denom and --denom-coefficient to set them manually.

from cosmos-exporter.

@sparkuss okay, thanks for confirming! I'll close it now then.

from cosmos-exporter.