Closed
Description
openedon Nov 14, 2019
Summary of Bug
When running the handshake calls 1 by 1 there is an unmarshal error but the transaction succeed.
gaiacli q ibc client header --node http://127.0.0.1:26657 --chain-id chainl2 > header.json
gaiacli --node http://185.227.108.95:26657 --chain-id vitwit tx ibc client update ibczeroclient header.json --from faucet --yes
returns
failed to unmarshall input into struct, checking for file...Password to sign with 'faucet':
but tx succeeds:
{"height":"0","txhash":"EF8D143FE31980E48DF273564001E4633AF945170FE870D3A187CDB00E487EAE","raw_log":"[{\"msg_index\":0,\"success\":true,\"log\":\"\",\"events\":[{\"type\":\"message\",\"attributes\":[{\"key\":\"action\",\"value\":\"update_client\"}]}]}]","logs":[{"msg_index":0,"success":true,"log":"","events":[{"type":"message","attributes":[{"key":"action","value":"update_client"}]}]}]}
Version
Steps to Reproduce
Use the guide here to create two chains:
https://gist.github.com/jackzampolin/2a7f90105fb5e778c3a3081681f10675
Then instead of the handshake, call:
gaiacli q ibc client path --node $NODE0 --chain-id $CHAINID0 > counterparty_prefix.json
gaiacli --node $NODE0 --chain-id $CHAINID0 tx ibc connection open-init $CONNID0 $CLIENT0 $CONNID1 $CLIENT1 \
counterparty_prefix.json 'x' --from validator-key --yes
gaiacli q ibc client header --node $NODE0 --chain-id $CHAINID0 > header.json
gaiacli --node $NODE1 --chain-id $CHAINID1 tx ibc client update $CLIENT1 header.json --from $KEY1 --yes
For Admin Use
- Not duplicate issue
- Appropriate labels applied
- Appropriate contributors tagged
- Contributor assigned/self-assigned
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Metadata
Assignees
Labels
No labels