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

fix!: force genOrBroadcastFn even when max-msgs != 0 #10477

Closed
wants to merge 3 commits into from

Conversation

0Tech
Copy link
Contributor

@0Tech 0Tech commented Nov 1, 2021

Description

If cli tx withdraw-all-rewards sends empty tx, the tx would be
rejected by validators because it has no msgs. However, the cli sends
empty tx only if one sets --max-msgs=0 which means it does not split
the msgs. When you set max-msgs with any positive number, the cli
does not send any tx, which may confuse you because you cannot get the
feedback indicating the address has no delegations.
This patch addresses the problem, by forcing genOrBroadcastFn when the
number of total msgs genreated is zero. It will provide the same user
experience with any max-msgs.


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 in the PR title
  • added ! to the type prefix if API or client breaking change
  • targeted the correct branch (see PR Targeting)
  • provided a link to the relevant issue or specification
  • followed the guidelines for building modules
  • included the necessary unit and integration tests
  • added a changelog entry to CHANGELOG.md
  • included comments for documenting Go code
  • 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 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)

@github-actions github-actions bot added C:CLI C:x/distribution distribution module related labels Nov 1, 2021
@0Tech 0Tech marked this pull request as ready for review November 1, 2021 09:51
@0Tech 0Tech force-pushed the 0Tech/cli-dist-withdraw-all branch from 9f2d0f0 to 632c858 Compare November 2, 2021 02:16
If cli tx withdraw-all-rewards sends empty tx, the tx would be
rejected by validators because it has no msgs. However, the cli sends
empty tx only if one sets `--max-msgs=0` which means it does not split
the msgs. When you set `max-msgs` with any positive number, the cli
does not send any tx, which may confuse you because you cannot get the
feedback indicating the address has no delegations.
This patch addresses the problem, by forcing genOrBroadcastFn when the
number of total msgs generated is zero. It will provide the same user
experience with any `max-msgs`.
@0Tech 0Tech force-pushed the 0Tech/cli-dist-withdraw-all branch from 632c858 to 3a791e3 Compare November 2, 2021 02:16
@0Tech 0Tech marked this pull request as draft November 2, 2021 02:17
@0Tech 0Tech marked this pull request as ready for review November 9, 2021 10:42
@github-actions
Copy link
Contributor

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Dec 25, 2021
@github-actions github-actions bot closed this Dec 31, 2021
@amaury1093 amaury1093 reopened this Jan 3, 2022
Copy link
Contributor

@amaury1093 amaury1093 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Re-opening. sorry @0Tech for the delay.


if chunkSize == 0 {
totalMessages := len(msgs)
if chunkSize == 0 || totalMessages == 0 {
return genOrBroadcastFn(clientCtx, fs, msgs...)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why would be broadcast a tx with 0 msgs if it's going to be rejected by the node? Shouldn't we just throw an error early?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C:CLI C:x/distribution distribution module related
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants