subquery / subql

SubQuery is an Open, Flexible, Fast and Universal data indexing framework for web3. Our mission is to help developers create the decentralised products of the future.
https://subquery.network
GNU General Public License v3.0
18.95k stars 331 forks source link

RangeError: index out of range: #2539

Open alexanderludwig opened 3 months ago

alexanderludwig commented 3 months ago

Prerequisites

Description

When running Celestia standard template receiving this issue: image

Details

These details can help to reproduce the environment the issue is occurring

image

alex@Alexanders-MBP celestia-starter % subql --version @subql/cli/5.2.3 darwin-arm64 node-v21.7.3

Local Environment: [You can get this information from executing subql version.] Query Version: [What is the version of the query service?] Indexer Version: [What is the version of the indexer service?] Network Details: chainId: "celestia", startBlock: 2143040, endpoint: [ "https://celestia-rpc.publicnode.com:443", ],

Steps to Reproduce

Example project: Just start the cosmos starter with described params.

Expected behavior: [What you expected to happen] Indexing

Actual behavior: [What actually happened] error message from above

Any other information

Is there any other information you would like to add?

stwiname commented 3 months ago

Hi @alexanderludwig

This is trying to decode a transaction using this function in a block but its not a RawTx. In order to help with this I would need to know the actual type to find a way to fix this.

stwiname commented 3 months ago

We have a similar issue that is being worked on but it doesn't seem to apply to your specific issue. https://github.com/subquery/subql-cosmos/pull/280

alexanderludwig commented 3 months ago

thanks for having a look at this @stwiname!! can you try running docker compose up for Celestia in cosmos-subql-starter? get the issue there without having done any modifications.

stwiname commented 3 months ago

Yes, I can reproduce the issue, we use cosmjs for decoding blocks but Celestia has different content in the transactions data. I've found some relevant issues from their organisation.

https://github.com/celestiaorg/celestia-app/issues/2715 https://github.com/celestiaorg/celestia-core/issues/1136