-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
R4R: Prompt user for confirmation when deleting ledger and offline keys #2923
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #2923 +/- ##
===========================================
- Coverage 56.29% 56.23% -0.06%
===========================================
Files 120 120
Lines 8411 8400 -11
===========================================
- Hits 4735 4724 -11
Misses 3354 3354
Partials 322 322 |
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.
See comments.
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.
tested (non-ledger) and LGTM.
if err != nil { | ||
return err | ||
} | ||
|
||
buf := client.BufferStdin() | ||
if info.GetType() == keys.TypeLedger || info.GetType() == keys.TypeOffline { | ||
if !viper.GetBool(flagYes) { |
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.
++
85a4917
to
2cc3b8f
Compare
CI failure is unrelated, once fixed on develop this LGTM. |
2cc3b8f
to
4898f1b
Compare
Add -y flag to skip confirmation. Also keybase should not handle confirmation input.
4898f1b
to
4a5b52a
Compare
… offline keys * Force password to 'yes' when deleting ledger-offline keys * Improve UX, better docs on removing offline/ledger keys * Ask for confirmation on offline/ledger keys deletion
* fix!: check v1 and v1beta1 MsgVote in VoteSpamDecorator cosmos/gaia#2912 introuced the VoteSpamDecorator. The implementation was not complete and only v1beta1 gov types were handled. The CLI supports v1 gov types so the validation was not sufficient. This commit expands the antehandler validation to allow correct processing of both v1 and v1beta1 messages. * appease linter * test: stop app from failing non-determinism test on gov vote * ante: handle edgecase with 0 minStakedTokens * appease linter
Closes: #2921
docs/
)PENDING.md
with issue #Files changed
in the github PR explorerFor Admin Use: