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

can't proto marshal <nil> error on submit-proposal cmd #10624

Closed
4 tasks
fedekunze opened this issue Nov 26, 2021 · 2 comments · Fixed by #11287
Closed
4 tasks

can't proto marshal <nil> error on submit-proposal cmd #10624

fedekunze opened this issue Nov 26, 2021 · 2 comments · Fixed by #11287
Assignees

Comments

@fedekunze
Copy link
Collaborator

Summary of Bug

When using the CLI to submit a proposal, it prints this error:

Error: invalid message: can't proto marshal <nil>

Version

v0.44.x

Steps to Reproduce

  • Install simd via make install
  • Try
simd tx gov submit-proposal --log_level info
Error: invalid message: can't proto marshal <nil>
Usage:
  simd tx gov submit-proposal [flags]
  simd tx gov submit-proposal [command]

Available Commands:
  cancel-software-upgrade Cancel the current software upgrade proposal
  community-pool-spend    Submit a community pool spend proposal
  param-change            Submit a parameter change proposal
  software-upgrade        Submit a software upgrade proposal

For Admin Use

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

I will work on this

@adu-web3
Copy link
Contributor

Is this owing to some other flags being not specified?
like --type and so on

@aleem1314 aleem1314 self-assigned this Jan 18, 2022
@mergify mergify bot closed this as completed in #11287 Feb 28, 2022
mergify bot pushed a commit that referenced this issue Feb 28, 2022
…s provided (#11287)

## Description

Closes: #10624 



---

### Author Checklist

*All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.*

I have...

- [ ] included the correct [type prefix](https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.json) in the PR title
- [ ] added `!` to the type prefix if API or client breaking change
- [ ] targeted the correct branch (see [PR Targeting](https://github.com/cosmos/cosmos-sdk/blob/master/CONTRIBUTING.md#pr-targeting))
- [ ] provided a link to the relevant issue or specification
- [ ] followed the guidelines for [building modules](https://github.com/cosmos/cosmos-sdk/blob/master/docs/building-modules)
- [ ] included the necessary unit and integration [tests](https://github.com/cosmos/cosmos-sdk/blob/master/CONTRIBUTING.md#testing)
- [ ] added a changelog entry to `CHANGELOG.md`
- [ ] included comments for [documenting Go code](https://blog.golang.org/godoc)
- [ ] updated the relevant documentation or specification
- [ ] reviewed "Files changed" and left comments if necessary
- [ ] confirmed all CI checks have passed

### Reviewers Checklist

*All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.*

I have...

- [ ] confirmed the correct [type prefix](https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.json) in the PR title
- [ ] confirmed `!` in the type prefix if API or client breaking change
- [ ] confirmed all author checklist items have been addressed 
- [ ] reviewed state machine logic
- [ ] reviewed API design and naming
- [ ] reviewed documentation is accurate
- [ ] reviewed tests and test coverage
- [ ] manually tested (if applicable)
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