-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
--generate-only broke between v0.33 and v0.34 #4131
Comments
I can reproduce |
It's a longstanding problem. We've made confusion between |
@davepuchyr All I can do for now is tentatively recommending a mitigation to your problem. Try the following:
|
Thanks @davepuchyr, but this is not a bug and is intended behavior, see: #3960. The goal was to have generate-only functionality be consistent across clients, both REST and CLI. You must provide a valid Bech32 cosmos address as input whenever performing generate-only. If you deem that it should not be consistent across both clients, please open another issue to allow further discourse. |
Thank-you for the quick response and the workaround, I can live with it. I agree with the goal of consistency. BTW, I did search for various forms of "generate-only" before submitting the issue. #3960 never came up. Regardless, I owe @alessio a beer! |
Thanks @davepuchyr. A valid search came up for me with query: "generate" :) Enjoy your 🍻 |
There is a similar in #6434 |
Summary of Bug
gaiacli txs work without the "--generate-only" flag but fail with the "--generate-only" flag yeilding
failed to get from fields: decoding bech32 failed: invalid bech32 string length 4
.Example of a successful execution:
Example of a failed execution with the only difference in the command being the "--generate-only" flag:
Version
Steps to Reproduce
Added the "--generate-only" flag to a gaiacli command.
For Admin Use
The text was updated successfully, but these errors were encountered: