You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We were trying to debug a header verification issue and in order to reproduce it we needed to know the effective target height for Latest. This is available as a trace message but we should bump it up.
Version
all
Steps to Reproduce
Run the hermes update client CLI without specifying the target and try to determine the height. If it fails there is no information. If it is succesful one can check the latest consensus state but even that is not 100% accurate.
For the record, the failure reported was:
~/bin/hermes update client --host-chain teritori-1 --client 07-tendermint-100
2024-09-12T05:17:35.175768Z INFO ThreadId(01) using default configuration from '/srv/hermes/.hermes/config.toml'
2024-09-12T05:17:35.187480Z INFO ThreadId(01) running Hermes v1.10.2+524ee6ce0
2024-09-12T05:17:35.269791Z ERROR ThreadId(34) foreign_client.build_update_client_and_send{client=cosmoshub-4->teritori-1:07-tendermint-100 target_query_height=latest height}:send_messages_and_wait_commit{chain=teritori-1 tracking_id=update client}:send_tx_with_account_sequence_retry{chain=teritori-1 account.sequence=37088}:estimate_gas: failed to simulate tx. propagating error to caller: gRPC call `send_tx_simulate` failed with status: status: Unknown, message: "failed to execute message; message index: 0: failed to verify header: cant trust new val set: invalid commit -- insufficient voting power: got 163690626, needed more than 163819643 [cosmos/ibc-go/[email protected]/modules/light-clients/07-tendermint/update.go:115] With gas wanted: '18446744073709551615' and gas used: '5818145' ", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "x-cosmos-block-height": "10576378"} }
2024-09-12T05:17:35.269845Z ERROR ThreadId(34) foreign_client.build_update_client_and_send{client=cosmoshub-4->teritori-1:07-tendermint-100 target_query_height=latest height}:send_messages_and_wait_commit{chain=teritori-1 tracking_id=update client}:send_tx_with_account_sequence_retry{chain=teritori-1 account.sequence=37088}: gas estimation failed or encountered another unrecoverable error error=gRPC call `send_tx_simulate` failed with status: status: Unknown, message: "failed to execute message; message index: 0: failed to verify header: cant trust new val set: invalid commit -- insufficient voting power: got 163690626, needed more than 163819643 [cosmos/ibc-go/[email protected]/modules/light-clients/07-tendermint/update.go:115] With gas wanted: '18446744073709551615' and gas used: '5818145' ", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "x-cosmos-block-height": "10576378"} }
ERROR foreign client error: error raised while updating client on chain teritori-1: failed sending message to dst chain: gRPC call `send_tx_simulate` failed with status: status: Unknown, message: "failed to execute message; message index: 0: failed to verify header: cant trust new val set: invalid commit -- insufficient voting power: got 163690626, needed more than 163819643 [cosmos/ibc-go/[email protected]/modules/light-clients/07-tendermint/update.go:115] With gas wanted: '18446744073709551615' and gas used: '5818145' ", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "x-cosmos-block-height": "10576378"} }
Acceptance Criteria
The target height information is visible to the user
For Admin Use
Not duplicate issue
Appropriate labels applied
Appropriate milestone (priority) applied
Appropriate contributors tagged
Contributor assigned/self-assigned
The text was updated successfully, but these errors were encountered:
Summary of Bug
We were trying to debug a header verification issue and in order to reproduce it we needed to know the effective target height for
Latest
. This is available as a trace message but we should bump it up.Version
all
Steps to Reproduce
Run the
hermes update client
CLI without specifying the target and try to determine the height. If it fails there is no information. If it is succesful one can check the latest consensus state but even that is not 100% accurate.For the record, the failure reported was:
Acceptance Criteria
The target height information is visible to the user
For Admin Use
The text was updated successfully, but these errors were encountered: