-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Conversation
9f2d0f0
to
632c858
Compare
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`.
632c858
to
3a791e3
Compare
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. |
There was a problem hiding this 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...) |
There was a problem hiding this comment.
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?
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 splitthe msgs. When you set
max-msgs
with any positive number, the clidoes 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...
!
to the type prefix if API or client breaking changeCHANGELOG.md
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...
!
in the type prefix if API or client breaking change