-
Notifications
You must be signed in to change notification settings - Fork 974
Add "Import recovery keys" button to Payments->Advanced->Recover #5809
Add "Import recovery keys" button to Payments->Advanced->Recover #5809
Conversation
cc/ @luixxiul |
Would you mind rebasing this on master? Thanks! |
@bbondy: no problem, rebased against latest |
@willy-b doh- needs another rebase. If you can get that done, I'll make sure to review in a timely manner |
@bsclifton , rebasing and adjusting for the upstream changes in the Recovery Key File format now |
OK @bsclifton , rebase is done and force-pushed here. (If needed to check something, the old branch was copied to https://github.com/willy-b/browser-laptop/tree/add-import-recovery-keys-button-4806-rebase-old ) Thanks! |
Very cool feature, @willy-b! 😄 Some notes after reviewing:
|
Don't necessarily re-review yet, one more commit coming! This commit just contains tests for saving and recovering the key file which I wanted to keep distinct. Thanks. |
OK @bsclifton, this should be ready for re-review. Everything in your previous comment should be fixed now. After review I'll do a rebase and force-push if it's OK with you. |
Any reason why we can't clear this out? I thin kthis already works? |
@posix4e I haven't had time to review NOTE: if it looks good, let's just tag with |
@bsclifton roger that |
Actually @bsclifton not sure what this commit does that we don't already @willy-b |
Hey @posix4e, thanks for taking a look. Re your question, there's a few commits here:
|
@willy-b wanna rebase then? |
Sure, rebasing now (just pushed a rebase but it was to a somewhat out of date master, and it turns out there have been changes to the brave test library since then, so resolving those conflicts now). The command for the new tests for the Payments -> Advanced modals is: |
Rebased against latest master, thanks. |
@willy-b can you update the commit that fixes #6263 to have the "Fixes #6263" keyword in the commit? 😄 Sorry for the extremely long turn-around here. I know all of us here at Brave are hustling on the open items for 0.13.0, which will be our first release with Chromium 54 (which has caused us to have major architectural changes). This is definitely an important fix and I'm excited about pulling it in (along with the other PRs for 0.13.1). |
hey @bsclifton
recommend merging this PR (w/ tests) rather than cherry-picking for #6263, just imho. |
heads up, 2 more pending PRs which may cause silent conflict when merged, bringing total to 3:
(if these are merged before this is, hold this until I or someone else tests it again. otherwise I think this is clear) |
Is this ready-for-merge, or do we need another review? |
This is ready-to-merge, unless any of #6455, #6456, or #6422 are merged first. (update 1/4/2017: also #6529) |
looks like you just rebased it and resolved conflicts yourself @bsclifton. thanks! I'll pull and test what you've got here then. |
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.
(finally had time to review)
Great work, @willy-b! 😄
I went through this pretty thoroughly and had a few updates which I made directly:
- rebased against master
- reverted changes from return => yield in
ledgerPanelTest.js
. These changes broke the tests for me. I verified reverting this works. - Removed unneeded .bind() in
ledgerPanelAdvancedPanelTest.js
(lint error was thrown; you may have pre-commit hooks disabled) - ran docs update task to properly update action descriptions (usually ran in post-commit hook)
- squashed it all down to 1 commit
I verified that all "Payments Panel" tests pass (ran multiple times) and updated the PR to show the other issue this resolves
thanks @bsclifton! |
FYI, #6455 just came in so may be silent conflict with that. |
@willy-b yup- understood, as you mentioned here #6447 (comment) 😄 |
hey @bsclifton, I couldn't get that branch to build for whatever reason -- probably a local issue. |
@willy-b no review needed 😄 I spent a good amount of time with it and feel confident enough to merge We've changed a few things about our PRs which may be confusing (especially since I am not sure we documented it!)
I'll make sure our docs get updated. Thanks again; great work on this 😄 |
Another rebase is needed and 7 failing tests need passing to be merged in 0.13.1-branch. |
(opens a file chooser dialog) fixes #4806 Includes tests for Ledger backup and recovery: - add advanced ledger panel tests file `test/components/ledgerPanelAdvancedPanelTest.js` - add tests for backup and recovery of wallet - add commands to Brave test client (`ipcOnce`, `ipcSendRendererSync`, and `translations`) client.translations: returns a map of all existing translations (current locale) to test client Import recovery keys success closes modals - successful import closes modals - and closing file chooser dialog does not trigger error screen fixes #6263 Import recovery keys shows error popover if keys are invalid or missing - error popover is displayed if paymentId / passphrase are missing or not UUIDs (ledger-client#recoverWallet should probably do validation too) - added tests for cases: one or both recovery keys missing from file a recovery key is not a UUID an empty recovery file
CI build had 3 errors; I ran each locally (one being a group of 6) and they each passed great. I removed the commit I had done to increase the timeout (it didn't improve things). Changes are good to go; merging to |
Nice work @willy-b 👍 |
Add "Import recovery keys" button that opens a file chooser dialog
fixes #4806
fixes #6263
git rebase -i
to squash commits (if needed).Test Plan
#4806 (comment)
Automated test plan