Skip to content

bug: chunk fetching error (unrecognized concrete type full name tm.StorageDepositEvent) #198

@matijamarjanovic

Description

@matijamarjanovic

We have started experiencing this error for certain transactions used to setup Volos development mode. The exact transactions executed are: full-workflow and multi-ops-workflow (from these files: https://github.com/stefann-01/gno/blob/feat/gnolend/volos-tests/test.mk and https://github.com/stefann-01/gno/blob/feat/gnolend/volos-tests/test.mk (in that order)).

Here are some error logs:

2025-09-09T13:55:15.599+0200    ERROR   fetcher fetch/fetch.go:227      error encountered during chunk fetch  {"error": "unable to get block results for block 15, unable to get block results, unable to unmarshal response bytes, amino: unrecognized concrete type full name tm.StorageDepositEvent\nunable to get block results for block 17, unable to get block results, unable to unmarshal response bytes, amino: unrecognized concrete type full name tm.StorageDepositEvent"}
github.com/gnolang/tx-indexer/fetch.(*Fetcher).FetchChainData
        /mnt/c/Users/matij/Projects/tx-indexer/fetch/fetch.go:227
main.(*waiter).wait.func2
        /mnt/c/Users/matij/Projects/tx-indexer/cmd/waiter.go:58
golang.org/x/sync/errgroup.(*Group).Go.func1
        /home/matijamarjanovic/go/pkg/mod/golang.org/x/[email protected]/errgroup/errgroup.go:93
2025-09-09T13:55:17.603+0200    ERROR   fetcher fetch/fetch.go:227      error encountered during chunk fetch  {"error": "unable to get block results for block 23, unable to get block results, unable to unmarshal response bytes, amino: unrecognized concrete type full name tm.StorageDepositEvent\nunable to get block results for block 25, unable to get block results, unable to unmarshal response bytes, amino: unrecognized concrete type full name tm.StorageDepositEvent\nunable to get block results for block 27, unable to get block results, unable to unmarshal response bytes, amino: unrecognized concrete type full name tm.StorageDepositEvent"}
github.com/gnolang/tx-indexer/fetch.(*Fetcher).FetchChainData
        /mnt/c/Users/matij/Projects/tx-indexer/fetch/fetch.go:227
main.(*waiter).wait.func2
        /mnt/c/Users/matij/Projects/tx-indexer/cmd/waiter.go:58
golang.org/x/sync/errgroup.(*Group).Go.func1
        /home/matijamarjanovic/go/pkg/mod/golang.org/x/[email protected]/errgroup/errgroup.go:93

Tx-indexer commit: 43f4b37
Master commit: 22632deb74dd2784f99baa9d758a856f2ff4d505

Version of master we were using before updating, where we haven't experienced this problem: 1618f4eb1698baaccb18e06a487d1da2475a197f

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Triage

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions