-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Closed
Labels
C: RelayerCOMPONENT: RelayerCOMPONENT: RelayerT: EnhancementTYPE: EnhancementTYPE: Enhancementgood first issueGood for newcomersGood for newcomers
Description
If you are relaying on several channels for a given path and an error occurs while sending msgs the logs generated are not entirely helpful because they lack the channel-ids, which means i cannot quickly see what channel this error occurred on.
Ex:
2023-03-27T18:40:11.670651Z error Error sending messages {"src_chain_id": "osmosis-1", "dst_chain_id": "quasar-1", "src_client_id": "07-tendermint-2703", "dst_client_id": "07-tendermint-1", "error": "rpc error: code = Unknown desc = rpc error: code = Unknown desc = failed to execute message; message index: 1: timeout packet verification failed: failed next sequence receive verification for client (07-tendermint-1): chained membership proof failed to verify membership of value: 0000000000000001 in subroot AD768F9A3EB69C5CCE8AFB65E97904E7777139056AC2C27BE52DAB356BC2D66A at index 0. Please ensure the path and value are both correct.: invalid proof [cosmos/ibc-go/v4@v4.3.0/modules/core/23-commitment/types/merkle.go:248] With gas wanted: '0' and gas used: '489260' : unknown request"}
Metadata
Metadata
Assignees
Labels
C: RelayerCOMPONENT: RelayerCOMPONENT: RelayerT: EnhancementTYPE: EnhancementTYPE: Enhancementgood first issueGood for newcomersGood for newcomers