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

Issue when using generate-only without chain-id #5303

Closed
4 tasks
haasted opened this issue Nov 12, 2019 · 0 comments · Fixed by #5348
Closed
4 tasks

Issue when using generate-only without chain-id #5303

haasted opened this issue Nov 12, 2019 · 0 comments · Fixed by #5348

Comments

@haasted
Copy link
Contributor

haasted commented Nov 12, 2019

Summary of Bug

There is a small issue when using the --generate-only flag and omitting the chain-id flag.

This is how it currently works (Release v0.37.4)

$ gaiacli tx send cosmos12d8c80nza2r2taavynm5u6q6t7rtdj58f5yqt5 cosmos1jm2xvf2r4qf5vmn873tzqzwyy76r54jrh9n8vs 5uatom --generate-only
{"type":"cosmos-sdk/StdTx","value":{"msg":null,"fee":{"amount":[],"gas":"0"},"signatures":null,"memo":""}}

ie. an empty transaction is output.

The cause of this is an error being ignored in cosmos-sdk/x/auth/client/utils/tx.go line 349 (current master).

If the line is changed to: return stdTx, err the output will be changed to the more informative:

$ gaiacli tx send cosmos12d8c80nza2r2taavynm5u6q6t7rtdj58f5yqt5 cosmos1jm2xvf2r4qf5vmn873tzqzwyy76r54jrh9n8vs 5uatom --generate-only
ERROR: chain ID required but not specified

Version

92d2dbe

Steps to Reproduce

Shown in bug description above.


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
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant