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

Simd: cannot protobuf JSON encode unsupported type: *tx.builder #7079

Closed
4 tasks
murthyvitwit opened this issue Aug 18, 2020 · 4 comments · Fixed by #7085
Closed
4 tasks

Simd: cannot protobuf JSON encode unsupported type: *tx.builder #7079

murthyvitwit opened this issue Aug 18, 2020 · 4 comments · Fixed by #7085
Assignees

Comments

@murthyvitwit
Copy link
Contributor

murthyvitwit commented Aug 18, 2020

Summary of Bug

Send tx is failing with message Error: cannot protobuf JSON encode unsupported type: *tx.builder

Version

master

Steps to Reproduce

Start a local testnet and execute

./simd tx bank send <mykey1> <to_address> 1000stake --from <mykey1> --chain-id <chain-id>


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
@murthyvitwit murthyvitwit changed the title Simid: cannot protobuf JSON encode unsupported type: *tx.builder Simd: cannot protobuf JSON encode unsupported type: *tx.builder Aug 18, 2020
@sahith-narahari sahith-narahari self-assigned this Aug 18, 2020
@anilcse
Copy link
Collaborator

anilcse commented Aug 18, 2020

Thanks @murthyvitwit for reporting this 👍

@alpe
Copy link
Contributor

alpe commented Aug 18, 2020

I can confirm this issue. I had the same error on OSX when upgrading wasmd to bcd9675 today.
On alpine linux the error was: The specified item could not be found in the keyring, exiting which is more accurate.

@aaronc
Copy link
Member

aaronc commented Aug 18, 2020

I'm not sure how this got missed by integration tests. TxConfig.TxJSONEncoder needs to be used instead

@aaronc
Copy link
Member

aaronc commented Aug 18, 2020

All this stuff will get exposed at build time once #7054 is merged btw.

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

Successfully merging a pull request may close this issue.

5 participants