Skip to content
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

ibc: fails when unpack ClientState #8059

Closed
4 tasks
yihuang opened this issue Dec 2, 2020 · 1 comment · Fixed by #8341
Closed
4 tasks

ibc: fails when unpack ClientState #8059

yihuang opened this issue Dec 2, 2020 · 1 comment · Fixed by #8341

Comments

@yihuang
Copy link
Collaborator

yihuang commented Dec 2, 2020

Summary of Bug

Do ibc-transfer using cli without passing --absolute-timeouts, it fails with error message:

AssertionError: Error: cannot unpack Any into ClientState *types.Any: failed unpacking protobuf message from Any

Version

0.40-rc3

Steps to Reproduce

  • start devnets connected with ibc
  • setup connections/channels with relayer
  • do a ibc-transfer with cli:
    chain-maind tx ibc-transfer transfer transfer demo0channel $receipet 1000denom --home data/ibc-0/node0 \
      --node tcp://localhost:26657 --keyring-backend test --from relayer --chain-id ibc-0 \
      -y --packet-timeout-height 1-2000 --packet-timeout-timestamp 0
    
    error message:
    AssertionError: Error: cannot unpack Any into ClientState *types.Any: failed unpacking protobuf message from Any
    
  • Add flag --absolute-timeouts, then works fine.

For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
@colin-axner
Copy link
Contributor

Thanks for opening this issue. Looks like the command is failing after trying to get the client state from the passed in channels

Most of our cli commands are untested and need some fixing, ref #6392

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants