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

setting --max-msgs along with --generate-only gives error #10841

Closed
atheeshp opened this issue Dec 27, 2021 · 0 comments · Fixed by #10842
Closed

setting --max-msgs along with --generate-only gives error #10841

atheeshp opened this issue Dec 27, 2021 · 0 comments · Fixed by #10842
Assignees

Comments

@atheeshp
Copy link
Contributor

atheeshp commented Dec 27, 2021

ref: #9407

setting --max-msgs along with --generate-only gives a weird error: Error: cannot use broadcast mode sync with max-msgs != 0. Why would setting the max message have any impact on which broadcast mode you can use?!

@atheeshp atheeshp mentioned this issue Dec 27, 2021
20 tasks
@atheeshp atheeshp changed the title setting --max-msgs along with --generate-only gives a weird error: Error: cannot use broadcast mode sync with max-msgs != 0. Why would setting the max message have any impact on which broadcast mode you can use?! setting --max-msgs along with --generate-only gives a weird error Dec 27, 2021
@atheeshp atheeshp changed the title setting --max-msgs along with --generate-only gives a weird error setting --max-msgs along with --generate-only gives error Dec 27, 2021
@mergify mergify bot closed this as completed in #10842 Jan 18, 2022
mergify bot pushed a commit that referenced this issue Jan 18, 2022
## Description

Closes: #10841 



---

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

Successfully merging a pull request may close this issue.

1 participant