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.

Sign up for GitHub

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

Jump to bottom

Empty response for invalid address on withdraw-all-rewards #363

Closed
4 tasks
egonspace opened this issue Oct 29, 2021 · 1 comment · Fixed by #364
Closed
4 tasks

Empty response for invalid address on withdraw-all-rewards #363

egonspace opened this issue Oct 29, 2021 · 1 comment · Fixed by #364
Assignees
@0Tech
Labels
A: bug Something isn't working A: improvement Changes in existing functionality

Comments

@egonspace
Copy link

egonspace commented Oct 29, 2021 •
edited
Loading

Summary

This is the feedback from the QA process of lbm v0.1.0-rc1.

simd responses empty for non-genesis account on withdraw-all-rewards command

simd tx distribution withdraw-all-rewards --from link1a35jrgnakgwarfc22c7wckh5hsn34r9r36v0a9 --keyring-backend test --home ~/.simapp/simapp0/ --chain-id sim

Problem Definition

Proposal

For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
@egonspace egonspace added the A: improvement Changes in existing functionality label Oct 29, 2021
@0Tech 0Tech self-assigned this Oct 29, 2021
@0Tech
Copy link
Collaborator

0Tech commented Oct 29, 2021

I cannot reproduce it on cosmos-sdk. I think it's a lbm-sdk specific bug. Working on it.

@egonspace egonspace added the A: bug Something isn't working label Oct 29, 2021
@0Tech 0Tech mentioned this issue Oct 29, 2021
Merged
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@0Tech 0Tech

Labels
A: bug Something isn't working A: improvement Changes in existing functionality
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: force genOrBroadcastFn even when max-msgs != 0 0Tech/finschia-sdk
2 participants
@0Tech @egonspace