-
Notifications
You must be signed in to change notification settings - Fork 332
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting client state was not found
error when querying client status on Celestia testnet
#3622
Comments
Note this still repros if I fallback to v0.34 compat mode
|
This error can occur if the client state returned by the node, encoded as a Protobuf I am not sure what's going wrong exactly with this client yet, we need to investigate further. In the meantime, if you could send us the full logs you get when you create the client that would be much appreciated! |
error decoding protobuf: error converting message type into domain type: the client state was not found
client state was not found
error when querying client status on Celestia testnet
Thanks for addressing all my feedback! I just tried to repro this error but this time I created a new client using my patch of hermes that falls back to v0.34 compat mode. When I do that, things work so I think my original issue may have been that I was trying to query a client that was created without my compat mode patch (?). Happy to close this issue as I think the root cause is already being fixed via #3623 Create client $ ./target/release/hermes create client --host-chain mocha-4 --reference-chain theta-testnet-001
2023-10-05T14:12:53.023867Z INFO ThreadId(01) using default configuration from '/Users/rootulp/.hermes/config.toml'
2023-10-05T14:12:53.025645Z INFO ThreadId(01) running Hermes v1.6.0+1c1cf0298-dirty
2023-10-05T14:12:54.841219Z WARN ThreadId(01) Unsupported tendermint version, will use v0.34 compatibility mode but relaying might not work as desired: unsupported Tendermint version reported by the node: 1.0.0-rc16
SUCCESS CreateClient(
CreateClient(
Attributes {
client_id: ClientId(
"07-tendermint-4",
),
client_type: Tendermint,
consensus_height: Height {
revision: 0,
height: 18233959,
},
},
),
) Query client $ ./target/release/hermes query client status --chain mocha-4 --client 07-tendermint-4
2023-10-05T14:13:53.099260Z INFO ThreadId(01) using default configuration from '/Users/rootulp/.hermes/config.toml'
2023-10-05T14:13:53.099473Z INFO ThreadId(01) running Hermes v1.6.0+1c1cf0298-dirty
2023-10-05T14:13:53.755571Z WARN ThreadId(01) Unsupported tendermint version, will use v0.34 compatibility mode but relaying might not work as desired: unsupported Tendermint version reported by the node: 1.0.0-rc16
SUCCESS Active |
Glad to hear, thanks for letting us know! |
Context
I'm trying to set up IBC clients between two tesnets:
Problem
I created a client with
now when I query it's state, I observe:
Given that error message, I'm not sure how to resolve.
The text was updated successfully, but these errors were encountered: